Anonymous's picture
Posted by Anonymous on November 21, 2008 at 1:13am
that's what is being proposed here:
some people from this group want to comment in that issue?
that's what is being proposed here:
some people from this group want to comment in that issue?
Comments
Is there anyone who can pick it up?
Can we find someone who can pick it up? I would, for sure, but I'm so new to coding Drupal modules that I'm probably not a good choice for it. (I'm a very long time psql user, though). I'd be happy to partner with someone who's more experienced at module development.
drupal experience not needed
You don't need to know much about Drupal to provide valuable help with PostgreSQL support - the main need is for testing patches - Damien linked to a very old critical bug with both Drupal 6 and 7 from the issue which prompted this thread, it's received pretty much zero testing from postgres users in several months - in that case, and many others, it's simply a case of applying the patch and confirming it works.
Similarly, if you and/or some others steps up to help with testing PostgreSQL - there's an army of people in the #drupal irc channel who'll help with coding questions or anything else you need to get up to speed. What we lack is 1. enough people who use postgresql (as opposed to maybe having it installed somewhere) to confirm bugs and test patches 2. one or two people who have a decent understanding of postgresql and ideally PDO to deal with some of the trickier bugs that come up - and most importantly, people who'll commit to doing so on a long term basis. At the moment, there's a very serious shortage of either, we don't have a shortage of people with Drupal expertise - it just happens that 99% of those people use MySQL.
I'm happy to help
OK, so I don't (yet) have a big site running Drupal/Postgres, but I am a PG expert, and I certainly could do testing of patches, and that sort of thing, and I am pretty committed to Postgres, so I'll be glad to adopt this for the long haul.
I'll go have a look at the bugs and patches, and figure out where to start. If anyone else is interested in helping out, let's figure out how to coordinate.
I am going to post my thoughts on this.
I am going to post my thoughts on this and link back when done. We are a website that gets 20k in hits a day and run solely on PostgreSQL so as far as I am concerned it would be a mistake for Drupal core not to support the database.
de-facto not supported
Book module has been broken on postgresql for months, in a stable release, simpletest has been broken on postgresql forever. So by default, we don't have proper postgresql support in Drupal core - I should note that the person who started that issue has been one of the more active people trying to improve support for it, but no-one has stepped in to help with these efforts who actually uses postgresql. So removing the driver from core would simply be confirming reality at this point.
I was going to jump in and
I was going to jump in and start testing some of the D7/pgsql patches, but am having troubles even getting the install to work. Does CVS HEAD install for anybody running pg 8.2? If not, are there pending patches I'm not finding to get up and running?
@jhedstrom I jumped in two
@jhedstrom
I jumped in two days ago.
The following issues were created:
Issue #1 :
http://drupal.org/node/337794#comment-1125219
Presently, after patch, jump to ISSUE #3:
http://drupal.org/node/337796#comment-1125317
Install a patch for Drupal Database, ISSUE #4:
http://drupal.org/node/338586
I don't know to what extent D7 supports PostgreSQL 8.2, as I am running 8.3
Well, I figured out why the
Well, I figured out why the install is failing (or at least one reason, as this is the first error it bombs out on).
http://drupal.org/node/330633
BTW, commenting out the
BTW, commenting out the query mentioned in http://drupal.org/node/330633 allows the install to finish.
thanks!
just wanted to say thanks to all those postgres people who've jumped in to help - you all rock! :-)