Have the same question myself. I have run in to minor bugs and limited support of postgres in the modules. I try to fix them myself, but combining efforts could be a good idea.
I do wonder just how many people (raw numbers or percentage) actually use PostgreSQL (or at least try to) as their database of preference with Drupal.
I prefer PostgreSQL myself and tried to use it initially, but have had to install MySQL and work with that in production for Drupal given the number of problems I have come across with pgsql that weren't there with mysql.
To say the least, the PostgreSQL implementation is less than mature. I wonder how, or if, it will get to the level of maturity that the MySQL code has.
I've run across a couple of errors here and there that I've easily patched, and not all modules support it, but I've been very happy. The big challenge has been connecting to the database in the secure environment I'm using, but once up and running, it's peachy. See gogoray.net (Drupal 5.1) and sjaconsulting.com (Drupal 4.6.3) for examples of various releases of Drupal running postgresql. I would have to say that the Drupal 5.1 experience is by far the easiest with respect to psql.
I just got started playing with Drupal (advise from a college and then a new business requirement that Drupal might fit), and I am very sad to see that its support for Postgres is painfully lacking.
It's not that I really hate MySQL, I just really hate that it has consistently blown up on me and lost data. I know a lot of people seem to get lucky and don't get to enjoy that fun experience ... maybe I've been getting their share?
I thought maybe it was our install or something, until it consistently happened on multiple servers, multiple applications, and then I found this link. We even tried switching the table type to InnoDB, but do _not_ try to do anything bigger than small imports with InnoDB ... our (then only a few) million INSERT refreshes were so slow that the refresh would be running still when the next one wanted to kick off! MyISAM is fast, just not reliable, and transactions have recently been added to MySQL, where in Postgres, they are very mature.
So, now I'm torn. Do I just give in and go the MySQL route and hope that it doesn't blow up on our customers' Drupal instances (we're talking about many instances in a multi-site environment), or do I slog through the poor Postgres support and do a lot of my own fixes ... and hope the module maintainers, etc, except the patches?
Also, going to MySQL again for something so critical means I have to figure out how to make MySQL cluster and HA'able ... anyone got any good links for that?
I would love for the users who would prefer Postgres to get together and see if we can put some weight behind our requests!
I use postgresql too, and here http://pugs.postgresql.org/ there is work in progress, where drupal is in most place.
Drupal had (rumours said it is the past) many mysqlish contributors. Postgresql users must work and revisit frequently, but with time, modules can become fully postgresql compliant.
Mediawiki did a very great job by adding postgresql backend support. Drupal must keep that backend in mind and let postgresql users optimize the queries and the mysqlish oriented code.
If you are an experienced PostgreSQL user, join and help out
If you are experiencing problems with modules using PostgreSQL, join and ask for help
If you are curious about PostgreSQL, join and ask questions!
Have the same question
Have the same question myself. I have run in to minor bugs and limited support of postgres in the modules. I try to fix them myself, but combining efforts could be a good idea.
How many even use PostgreSQL?
I do wonder just how many people (raw numbers or percentage) actually use PostgreSQL (or at least try to) as their database of preference with Drupal.
I prefer PostgreSQL myself and tried to use it initially, but have had to install MySQL and work with that in production for Drupal given the number of problems I have come across with pgsql that weren't there with mysql.
To say the least, the PostgreSQL implementation is less than mature. I wonder how, or if, it will get to the level of maturity that the MySQL code has.
FYI, I'm in the process of
FYI, I'm in the process of building a few sites and am using PostgreSQL. :-)
Using postgresql in multiple production sites
I've run across a couple of errors here and there that I've easily patched, and not all modules support it, but I've been very happy. The big challenge has been connecting to the database in the secure environment I'm using, but once up and running, it's peachy. See gogoray.net (Drupal 5.1) and sjaconsulting.com (Drupal 4.6.3) for examples of various releases of Drupal running postgresql. I would have to say that the Drupal 5.1 experience is by far the easiest with respect to psql.
aigeanta
I too use PostgreSQL :(
I too use PostgreSQL :(
Broken Postgres support giving me headaches
I just got started playing with Drupal (advise from a college and then a new business requirement that Drupal might fit), and I am very sad to see that its support for Postgres is painfully lacking.
It's not that I really hate MySQL, I just really hate that it has consistently blown up on me and lost data. I know a lot of people seem to get lucky and don't get to enjoy that fun experience ... maybe I've been getting their share?
I thought maybe it was our install or something, until it consistently happened on multiple servers, multiple applications, and then I found this link. We even tried switching the table type to InnoDB, but do _not_ try to do anything bigger than small imports with InnoDB ... our (then only a few) million INSERT refreshes were so slow that the refresh would be running still when the next one wanted to kick off! MyISAM is fast, just not reliable, and transactions have recently been added to MySQL, where in Postgres, they are very mature.
So, now I'm torn. Do I just give in and go the MySQL route and hope that it doesn't blow up on our customers' Drupal instances (we're talking about many instances in a multi-site environment), or do I slog through the poor Postgres support and do a lot of my own fixes ... and hope the module maintainers, etc, except the patches?
Also, going to MySQL again for something so critical means I have to figure out how to make MySQL cluster and HA'able ... anyone got any good links for that?
I would love for the users who would prefer Postgres to get together and see if we can put some weight behind our requests!
I use postgresql too, and
I use postgresql too, and here http://pugs.postgresql.org/ there is work in progress, where drupal is in most place.
Drupal had (rumours said it is the past) many mysqlish contributors. Postgresql users must work and revisit frequently, but with time, modules can become fully postgresql compliant.
Mediawiki did a very great job by adding postgresql backend support. Drupal must keep that backend in mind and let postgresql users optimize the queries and the mysqlish oriented code.
Me too
I use PostgreSQL.
A perfect database.
Consider joining
Consider joining http://groups.drupal.org/postgresql
If you are an experienced PostgreSQL user, join and help out
If you are experiencing problems with modules using PostgreSQL, join and ask for help
If you are curious about PostgreSQL, join and ask questions!