<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><br></div><div>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.</div><div><br></div><div>Here's the client's development/production environment:</div><div><br></div><div><ul class="MailOutline"><li>Debian Lenny (5.0) host environment</li><li>Debian packaging for deployment</li><li>Drupal 6 framework</li><li>PostgreSQL 8.3 database</li><li>Git source control</li><li>Apache Solr 1.4 for search and related artist matching</li><li>Amazon S3 + CloudFront for storage and streaming of videos</li><li>FFMpeg for encoding of uploaded videos</li><li>JWPlayer for playback (looking to replace this in a future phase))</li><li>Apache and Nginx web servers (although development can be done with just Apache)</li><li>PHP 5.2</li></ul></div><div><br></div><div>They know what they're doing!</div><div><br></div><div>Here's what I read about PostgreSQL on <a href="http://Drupal.org">Drupal.org</a>:</div><div><br></div><div>(From <a href="http://drupal.org/node/33171">http://drupal.org/node/33171</a>)</div><div><br></div><div></div><blockquote type="cite"><div>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.<br><br>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.</div></blockquote><div><br></div><div>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.</div><div><br></div><div>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!</div><div><br></div><div>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.</div><div><br></div><div>What do you think?</div><div><br></div><div><div>Thank you,</div><div><br></div><div>Kevin</div></div><div><br></div><div><font face="Courier New" size="3" class="f1">--- </font><br><font face="Courier New" size="3" class="f1"></font><br><font face="Courier New" size="3" class="f1">Quevin, LLC</font><br><font face="Courier New" size="3" class="f1"> <a href="http://Quevin.com">Quevin.com</a></font><br><font face="Courier New" size="3" class="f1"> <a href="http://twitter.com/Quevin">twitter.com/Quevin</a></font><br><font face="Courier New" size="3" class="f1"> <a href="http://linkedin.com/in/quevin">linkedin.com/in/quevin</a></font></div></body></html>