Khalid wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>This is exactly the problem: those who use Drupal on PostgreSQL must
<br>be the ones who would resolve the SQL differences, test and debug patches,<br>...etc. <br><br>They are the ones that have a vested interest in it more than the rest<br>of us. All of us want a cross platform cross database CMS, but the testing
<br>work must be done by those who use PostgreSQL.<br><br><font color="#888888"></font></blockquote><div><br>Which brings us back to the original topic of this thread. And the fact there's a release critical issue[1] which has been waiting for 4 days and 16 hours now for a quick test on postgresql. I don't think I need to point out the irony of this situation.
<br><br>1. <a href="http://drupal.org/node/164532">http://drupal.org/node/164532</a> Improve table indices for common queries.<br><br><br><br></div></div><br>