[consulting] Drupal: MySQL vs. PostgreSQL

[Christian Pearce]

I worked with a customer that only ran PostgreSQL. I just routinely submitted patches to the contributed that didn't support postgresql. I mostly had to deal with the fact the install files were not supported. Every once in a while people would use functions that only existing in MySQL. After a while I just routinely found people who already had a patch submitted in the support queue. it wasn't much of a pain at all. 

----- "Brian Vuyk" <brian at brianvuyk.com> wrote: 
> Kevin, 
> 
> PostegreSQL is a great SQL backend, and has a bunch of advantages over MySQL for larger sites. However, in Drupal usage, it has two main strikes against it: 
> 
> 1. The majority of Drupal developers use MySQL. A somewhat lesser number use Postgres. As a result, Postgres-specific bugs in core aren't quashed quite as quickly as MySQL-specific bugs. 
> 
> 2. While Drupal has a commitment to be compatible with Postegres, contrib can vary quite a bit. That is, as often as not, your contrib modules will have SQL queries in them that just plain don't work with Postgres. 
> 
> Of these two problems, I think the lack of compatibility in contrib is the one you would deal with more. At least, you would likely find yourself in a position to be writing Postgres compatibility patches for modules you use. 
> 
> Brian 
> 
> On 10-07-20 07:20 PM, Kevin Davison wrote: 

I'm not very familiar with the use of PostgreSQL with Drupal, as I tend to use Pressflow with MySQL on most projects. I read about the advantages and disadvantages, but not sure how to compare a clustered DB with PostgreSQL and Pressfow running on Pantheon with MySQL optimized, perhaps on multiple DB servers. It looks like there are various issues with contributed modules & PostgreSQL, and that doesn't sound like much fun to deal with. 

> 
So now I have a potential client who needs help with PostgreSQL in the mix, and I'm not sure if I should get involved. 

> 
Here's the client's development/production environment: 

> 


    • Debian Lenny (5.0) host environment 
    • Debian packaging for deployment 
    • Drupal 6 framework 
    • PostgreSQL 8.3 database 
    • Git source control 
    • Apache Solr 1.4 for search and related artist matching 
    • Amazon S3 + CloudFront for storage and streaming of videos 
    • FFMpeg for encoding of uploaded videos 
    • JWPlayer for playback (looking to replace this in a future phase)) 
    • Apache and Nginx web servers (although development can be done with just Apache) 
    • PHP 5.2 


> 
They know what they're doing! 

> 
Here's what I read about PostgreSQL on Drupal.org : 

> 
(From http://drupal.org/node/33171 ) 

> 


First off you have to ask yourself is it really worth it? In most cases no absolutely not, MySQL is just fine for sites that are small and want to remain that way, this includes personal sites and blogs etc. 
> 
> PostgreSQL's real strength at least in my opinion comes from its ability to seamlessly cluster, thereby distributing the load among many DB servers rather than bogging down a single server. If you have a big website with lots of traffic and have the resources for multiple servers, then PostgreSQL is definitely the way to go. 

> 
This potential client has a lot of data, with the potential for a lot of traffic. Their current configuration may be ideal, as far as I know right now. 

> 
And I've been really happy with staging development on WebEnabled, but they don't support PostgreSQL yet. I don't even have PostgreSQL installed on my local development environment! 

> 
So I'm asking the Drupal community about this one. Perhaps I need to learn more about PostgreSQL, or I just need to stick with what I know best (as an intermediate at MySQL). And I may need some help from Developers who do know more. 

> 
What do you think? 

> 

Thank you, 

> 
Kevin 

> 
--- 
> 
> Quevin, LLC 
> Quevin.com 
> twitter.com/Quevin 
> linkedin.com/in/quevin _______________________________________________
consulting mailing list consulting at drupal.org http://lists.drupal.org/mailman/listinfo/consulting 
> 
> _______________________________________________ consulting mailing list consulting at drupal.org http://lists.drupal.org/mailman/listinfo/consulting 
> 

-- 



xforty technologies 
Christian Pearce 
888-231-9331 x1119 
http://xforty.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20100726/1658382e/attachment.html