Guys/gals ...<br><br>Please. <br><br>No one is advocating that Drupal be MySQL only. No one is advocating<br>that we rip out PostgreSQL support from Drupal. <br><br>Being database agnostic is a good thing. We all agree on that.
<br><br>The point Karoly is trying to make is that PostgreSQL keeps lagging behind<br>because of lack of testing, and that holds back otherwise good patches.<br><br>The noble people who are going out of their way to test PostgreSQL even 
<br>though they don&#39;t use it are doing a good thing. But is it enough? Have the<br>list of PostgreSQL issues diminished because of that?<br><br>Remember way back when, 3 years ago, we had MS SQL support in core.<br>Look at it here:
<br><a href="http://cvs.drupal.org/viewvc.py/drupal/drupal/database/database.mssql?hideattic=0&amp;view=log">http://cvs.drupal.org/viewvc.py/drupal/drupal/database/database.mssql?hideattic=0&amp;view=log</a><br><br>What happened? It went the way of the dodo. Unless something is done, 
<br>PostgreSQL risks the same fate. And people who are already busy switching <br>to PostgreSQL is not a sufficiently scalable answer.<br><br>If there are any PostgreSQL users (or Oracle, or DB2 or MS SQL), then they<br>
either have to provide the manpower for the tests or pay testers to ensure their<br>
stuff works for future releases.<br>
<br>Related point: We are talking here about just support for another database, not<br>supporting big sites with database optimization, ...etc. <br>