Hello,
I'm working on enterprise GIS application on open source PHP and need to implement PostgreSQL 9.3.x and PostGIS it's one of the extension.
So i urge cpanel team to implement this in future.
-Naitik
Improved PostgreSQL support
Open Discussion
I would like to see cPanel create and maintain its own PostgreSQL repository, much like how MySQL is currently handled, thus allowing server admins to give their users access to versions of PostgreSQL that are newer than what's available in the OS repositories.
This would allow admins to more easily upgrade to newer versions of the software, regardless of which OS they're on, without having to hack system files or wait for the OS developers to decide a version is stable enough to force an upgrade on everyone.
At times, PostgreSQL has introduced new features that would be widely useful to many (such as native full-text searching), but it's hard for developers to take advantage of those features when the majority of people using PostgreSQL will be stuck on an older version not supporting those features.
It should also be noted that PostgreSQL maintains its own repos for CentOS, Fedora and RHEL, so they have RPMs available for those OSes for the latest versions of PostgreSQL even when the official OS repos don't have those versions available. It might be easier to use these repos instead of trying to maintain your own.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Thank you guys for your engagement! It's always interesting to hear new feedback, and this is definitely triggering some internal discussions. For now we haven't seen enough community interest to put this on the roadmap yet. If you know of people who are interested in seeing this happen that haven't voted here, I encourage you to reach out to them. The most interest we see here, the more likely it is that we'll take action.
Thanks again for your involvement!
Thank you guys for your engagement! It's always interesting to hear new feedback, and this is definitely triggering some internal discussions. For now we haven't seen enough community interest to put this on the roadmap yet. If you know of people who are interested in seeing this happen that haven't voted here, I encourage you to reach out to them. The most interest we see here, the more likely it is that we'll take action.
Thanks again for your involvement!
At this time, cPanel & WHM does not distribute our own build/RPM of PostgreSQL. As a result, the version utilized with a cPanel & WHM server is strictly limited to the version distributed by the operating system vendor. It is that version and distribution in which we ensure our product supports.
At the time of this writing, this is:
CentOS/RHEL 5 = PostgreSQL 8.1
CentOS/RHEL 6 = PostgreSQL 8.4
It appears the RHEL 7 Beta presently distributes PostgreSQL 9.2, therefore current expectations are to support PostgreSQL 9.2 with CentOS/RHEL 7 unless the distributed version changes between now and the OS' official releases.
Support for PostgreSQL 9.3+ would, at the very least, require that we produce, maintain, and distribute our own RPM. While this is not out of the question, there are no current plans to do so. Please continue to provide feedback and discussion on this to demonstrate demand and use cases.
At this time, cPanel & WHM does not distribute our own build/RPM of PostgreSQL. As a result, the version utilized with a cPanel & WHM server is strictly limited to the version distributed by the operating system vendor. It is that version and distribution in which we ensure our product supports.
At the time of this writing, this is:
CentOS/RHEL 5 = PostgreSQL 8.1
CentOS/RHEL 6 = PostgreSQL 8.4
It appears the RHEL 7 Beta presently distributes PostgreSQL 9.2, therefore current expectations are to support PostgreSQL 9.2 with CentOS/RHEL 7 unless the distributed version changes between now and the OS' official releases.
Support for PostgreSQL 9.3+ would, at the very least, require that we produce, maintain, and distribute our own RPM. While this is not out of the question, there are no current plans to do so. Please continue to provide feedback and discussion on this to demonstrate demand and use cases.
2 votes in over a year and no response from cPanel devs... I guess PostgreSQL support isn't that important.
2 votes in over a year and no response from cPanel devs... I guess PostgreSQL support isn't that important.
PGSQL 9.x support is very important for cPanel servers. I am using cPanel with Phusion Passenger 4 Enterprise and soon 5 (we're working through some final bugs for the b2 release) and it is heating up to be a fantastic platform for Ruby, Python, and NodeJS app deployment. To this end, it would be exceptionally useful to have a nice solution for PostgreSQL in the mix already for us vs this poor level of support that presently exists.
PGSQL 9.x support is very important for cPanel servers. I am using cPanel with Phusion Passenger 4 Enterprise and soon 5 (we're working through some final bugs for the b2 release) and it is heating up to be a fantastic platform for Ruby, Python, and NodeJS app deployment. To this end, it would be exceptionally useful to have a nice solution for PostgreSQL in the mix already for us vs this poor level of support that presently exists.
Other important information is that PostgreSQL 8.4 reached its EOL (End of life) on July, 2014. So it is extremely important to upgrade to 9.x version.
Please give a high priority for this request.
Other important information is that PostgreSQL 8.4 reached its EOL (End of life) on July, 2014. So it is extremely important to upgrade to 9.x version.
Please give a high priority for this request.
PostgreSQL support is paramount. We have been dumping MySQL support for everything possible right now on our cPanel server and have manually installed PGSQL. It would be exceptionally useful to have a current release integrated vs having to manually maintain it.
PostgreSQL support is paramount. We have been dumping MySQL support for everything possible right now on our cPanel server and have manually installed PGSQL. It would be exceptionally useful to have a current release integrated vs having to manually maintain it.
yes it seems a good idea !
yes it seems a good idea !
Please, consider supporting newer versions of PostgreSQL.
Thank you
Please, consider supporting newer versions of PostgreSQL.
Thank you
I'd like to see support for newer versions of PostgreSQL as well. Also, it's worth noting that PostgreSQL offers their own pre-built packages for Red Hat distros (RHEL, CentOS, Fedora, etc.), SuSE/OpenSuSE, Ubuntu and Debian, so you could possibly use those instead of having to maintain your own.
I'd like to see support for newer versions of PostgreSQL as well. Also, it's worth noting that PostgreSQL offers their own pre-built packages for Red Hat distros (RHEL, CentOS, Fedora, etc.), SuSE/OpenSuSE, Ubuntu and Debian, so you could possibly use those instead of having to maintain your own.
Is there any way to custom install it and integrate it with phppgadmin and cpanel
Is there any way to custom install it and integrate it with phppgadmin and cpanel
As a postgresql user I want to add my vote and comments to this. MariaDB is fine for some things but when we need an open source equivalent of DB2, SQL server PostgreSQL is the choice.
First, I understand that cPanel suports what's installed by the OS however, given the long lifetime of products like Centos/RH it's not realistic to assume that's acceptable. During the lifetime of the server not only postgresql but other applications will be updated to take advantage of security fixes, replacing EOL software, and being able to use the new features. This happens on any OS and with any database be it postgresql, DB2, SQL Server, etc. cPanel needs to recognize this.
Second as for a custom cPanel version - NO!!!! That would be a disaster tying up cPanel resources and adding more time before we can upgrade. Postgres provides RPMs for almost every distribution availalbe. cPanel needs to leverage those and simply install them. It appears EasyApache 4 is trying to make more use of the yum install system to leverage what the server provides and not try and create complcated messy add-ons that break.
Finally, I do not know all the inner workings of cPanel and WHM but it seems that installpostgresql is overkill and not very smart. From what I can gather in first trying to make cPanel work with 9.5 and then updating 9.2 to 9.5 it appears the scripts make some bad assumptions such as where the data directory is and where the pgsql bin directory is. As far as I can tell that's all you need to fix - put those where cPanel thinks they should be and it works. That's not bad but when we are not given a chance to input that that is bad. I really don't understand why we can't install PostgreSQL and then fill out a WHM page giving the location of the data and bin directories. Once that's done we can either fill out the pg_hba.conf file ourself or use the WHM initialization section.
Under the KISS principle let us mange and setup the databases from the server and all cPanel does is show the status, allow us to configure the pg_hba.conf file, map users, and change the postgres user pastword. On the user's cPanel side just keep it as is with the database wizard and maintenance pages and phpPGAdmin. Make cPanel leave the rest of the stuff alone.
I just finished an upgrade from 9.2 to 9.5 on Centos 7.2 (1511) and cPanel database creation and management works as does phpPGAdmin. The only thing that doesn't work is that WHM thinks the server is not running but since everything else works I really don't care. I can administer the database myself and just use cPanel DB Wizard to create databases and users and phpPGAdmin to manipulate the database tables.
I hope that cPanel will make this a high priority issue.
As a postgresql user I want to add my vote and comments to this. MariaDB is fine for some things but when we need an open source equivalent of DB2, SQL server PostgreSQL is the choice.
First, I understand that cPanel suports what's installed by the OS however, given the long lifetime of products like Centos/RH it's not realistic to assume that's acceptable. During the lifetime of the server not only postgresql but other applications will be updated to take advantage of security fixes, replacing EOL software, and being able to use the new features. This happens on any OS and with any database be it postgresql, DB2, SQL Server, etc. cPanel needs to recognize this.
Second as for a custom cPanel version - NO!!!! That would be a disaster tying up cPanel resources and adding more time before we can upgrade. Postgres provides RPMs for almost every distribution availalbe. cPanel needs to leverage those and simply install them. It appears EasyApache 4 is trying to make more use of the yum install system to leverage what the server provides and not try and create complcated messy add-ons that break.
Finally, I do not know all the inner workings of cPanel and WHM but it seems that installpostgresql is overkill and not very smart. From what I can gather in first trying to make cPanel work with 9.5 and then updating 9.2 to 9.5 it appears the scripts make some bad assumptions such as where the data directory is and where the pgsql bin directory is. As far as I can tell that's all you need to fix - put those where cPanel thinks they should be and it works. That's not bad but when we are not given a chance to input that that is bad. I really don't understand why we can't install PostgreSQL and then fill out a WHM page giving the location of the data and bin directories. Once that's done we can either fill out the pg_hba.conf file ourself or use the WHM initialization section.
Under the KISS principle let us mange and setup the databases from the server and all cPanel does is show the status, allow us to configure the pg_hba.conf file, map users, and change the postgres user pastword. On the user's cPanel side just keep it as is with the database wizard and maintenance pages and phpPGAdmin. Make cPanel leave the rest of the stuff alone.
I just finished an upgrade from 9.2 to 9.5 on Centos 7.2 (1511) and cPanel database creation and management works as does phpPGAdmin. The only thing that doesn't work is that WHM thinks the server is not running but since everything else works I really don't care. I can administer the database myself and just use cPanel DB Wizard to create databases and users and phpPGAdmin to manipulate the database tables.
I hope that cPanel will make this a high priority issue.
100% agree with Brett's last remarks. Super big need here as well. It's a real hassle to manage it outside of the system as we have to at present.
100% agree with Brett's last remarks. Super big need here as well. It's a real hassle to manage it outside of the system as we have to at present.
I've merged these two requests to allow us to better and more accurately track interest from the community. I know this isn't on our roadmap currently, but I'll bring it to the attention of our lead product owner for further consideration. Thanks so much for your continued feedback.
I've merged these two requests to allow us to better and more accurately track interest from the community. I know this isn't on our roadmap currently, but I'll bring it to the attention of our lead product owner for further consideration. Thanks so much for your continued feedback.
Thank you.
Thank you.
Thanks @cpanelbenny! This is one of those things that advanced application and Ruby developers find extremely valuable. Hitherto, cPanel has not been a platform that caters to Ruby (Rails, etc.) developers except for those of us who are willing to extend the platform with our own personal investigation and effort. PGSQL is one of those needs that we have as we generally prefer this in comparison to MySQL. Having PGSQL is just another powerful attractor towards bringing Ruby and Rails developers over to the platform.
Thanks @cpanelbenny! This is one of those things that advanced application and Ruby developers find extremely valuable. Hitherto, cPanel has not been a platform that caters to Ruby (Rails, etc.) developers except for those of us who are willing to extend the platform with our own personal investigation and effort. PGSQL is one of those needs that we have as we generally prefer this in comparison to MySQL. Having PGSQL is just another powerful attractor towards bringing Ruby and Rails developers over to the platform.
Thank you guys for your engagement! It's always interesting to hear new feedback, and this is definitely triggering some internal discussions. For now we haven't seen enough community interest to put this on the roadmap yet. If you know of people who are interested in seeing this happen that haven't voted here, I encourage you to reach out to them. The most interest we see here, the more likely it is that we'll take action.
Thanks again for your involvement!
Thank you guys for your engagement! It's always interesting to hear new feedback, and this is definitely triggering some internal discussions. For now we haven't seen enough community interest to put this on the roadmap yet. If you know of people who are interested in seeing this happen that haven't voted here, I encourage you to reach out to them. The most interest we see here, the more likely it is that we'll take action.
Thanks again for your involvement!
Postgresql 8.4 now is not supported and outdated: https://www.postgresql.org/support/versioning/
When I try $/scripts/installpostgres
It installs 8.4 by default ! I found difficulties to upgrade to the newest version
Please facilitate supporting postgresql new versions
Postgresql 8.4 now is not supported and outdated: https://www.postgresql.org/support/versioning/
When I try $/scripts/installpostgres
It installs 8.4 by default ! I found difficulties to upgrade to the newest version
Please facilitate supporting postgresql new versions
+1 for better support
For some time now we have been making use of postgresql.org provided RPMs up to version 9.6 which have been working fine.
Unfortunately cPanel scripts can't handle version 10. Would be great if we could just get some fixes for that.
+1 for better support
For some time now we have been making use of postgresql.org provided RPMs up to version 9.6 which have been working fine.
Unfortunately cPanel scripts can't handle version 10. Would be great if we could just get some fixes for that.
Also will be good if phpPgAdmin will be in WHM too like phpMyAdmin.
Also will be good if phpPgAdmin will be in WHM too like phpMyAdmin.
Hi do we have any idea if this can be improved? Can we get a update on the status of this if its still a thought?
Hi do we have any idea if this can be improved? Can we get a update on the status of this if its still a thought?
Something I was thinking of is using a remote Postgresql server as an option. Something like AWS or Jelastic could simplify administration of this kind of database.
Something I was thinking of is using a remote Postgresql server as an option. Something like AWS or Jelastic could simplify administration of this kind of database.
Do we have any updates for this? I know a lot of users and providers would love for this to be improved
Do we have any updates for this? I know a lot of users and providers would love for this to be improved
In fact I think it is interesting for the community, the point is that they are so limited, they end up taking other alternatives, I myself have been waiting for more than 3 years for support for decent postgresql.
Postgres is already in version 13 and the default one based on RPM packages is Postgres 9.2.
Not to mention that pgAdmin is very outdated.
In fact I think it is interesting for the community, the point is that they are so limited, they end up taking other alternatives, I myself have been waiting for more than 3 years for support for decent postgresql.
Postgres is already in version 13 and the default one based on RPM packages is Postgres 9.2.
Not to mention that pgAdmin is very outdated.
Any predictions for that? We are already in version 13 of PostgreSQL and I don't see any updates from cPanel
Any predictions for that? We are already in version 13 of PostgreSQL and I don't see any updates from cPanel
Honestly, given the lack of movement by cPanel, if you want a current version of PostgreSQL your Administrator can add the PostgreSQL repo to CentOS. Last I checked it went as far back as 9.5, all the way to current. Just remember to set up a daily cron job to keep the rpms up to date, as the cPanel upcp command likely won’t update packages from third party repos.
Honestly, given the lack of movement by cPanel, if you want a current version of PostgreSQL your Administrator can add the PostgreSQL repo to CentOS. Last I checked it went as far back as 9.5, all the way to current. Just remember to set up a daily cron job to keep the rpms up to date, as the cPanel upcp command likely won’t update packages from third party repos.
I've been waiting for years too in order to have the software updated, the problem is not related only to Postgres but also to other cPanel features. After 8 years, I think that the only way to express importance on this theme is to change provider. I already switched all my servers to another control panel. I hope to return back to cPanel in future because the stability (stability does not mean old software but a well tested system), but with this slowness I don't think that will happen soon :(
I've been waiting for years too in order to have the software updated, the problem is not related only to Postgres but also to other cPanel features. After 8 years, I think that the only way to express importance on this theme is to change provider. I already switched all my servers to another control panel. I hope to return back to cPanel in future because the stability (stability does not mean old software but a well tested system), but with this slowness I don't think that will happen soon :(
Current cpanel support for Postgresql, which claims to be "the most world's advanced open source database" is a pity, not to say a shame. We must often look for workarounds, and I'm sorry to say that I'm already looking for web hostings providing decent postgresql features to replace all of my current hostings based on cpanel.
Current cpanel support for Postgresql, which claims to be "the most world's advanced open source database" is a pity, not to say a shame. We must often look for workarounds, and I'm sorry to say that I'm already looking for web hostings providing decent postgresql features to replace all of my current hostings based on cpanel.
I do want to point out that cPanel has only ever supported the version of PostgreSQL provided by the operating system, this means that if you're on CentOS 8 the version you'd have available is 10. Further to that cPanel does not use its own MariaDB or MySQL repositories. With that being said, I do believe there is room for improvement here and it is something that we're looking into in terms of improving support for non-MySQL/MariaDB database management systems, though there is work that must be completed before that can be done. While I do feel comfortable saying that this among other improvements in this area is on our roadmap, I don't feel comfortable telling you that it will be this year. More than likely this will be something that will be looked into more in-depth next year, once some rather large projects already being worked on are completed.
I do want to point out that cPanel has only ever supported the version of PostgreSQL provided by the operating system, this means that if you're on CentOS 8 the version you'd have available is 10. Further to that cPanel does not use its own MariaDB or MySQL repositories. With that being said, I do believe there is room for improvement here and it is something that we're looking into in terms of improving support for non-MySQL/MariaDB database management systems, though there is work that must be completed before that can be done. While I do feel comfortable saying that this among other improvements in this area is on our roadmap, I don't feel comfortable telling you that it will be this year. More than likely this will be something that will be looked into more in-depth next year, once some rather large projects already being worked on are completed.
Replies have been locked on this page!