[development] Do not let postgresql hold back great patches

Ken Rickard agentrickard at gmail.com
Sun Nov 11 22:31:25 UTC 2007

Is there a reliable way to search for patches requiring pgSQL testing?

Perhaps these sorts of things should be committed and then separate
issues opened for pgSQL testing?

In the case of this issue, ALTER IGNORE will not work on pgSQL. [Will
follow-up there.]

It is also possible (and quick) to run EXPLAIN against pgSQL if we
have a list of queries that I could test.

- Ken Rickard

Note: Not a pgSQL guru, but have it installed on the Mac.

On Nov 11, 2007 5:17 PM, Karoly Negyesi <karoly at negyesi.net> wrote:
> In my opinion, any patch should be committable to core once it works
> on mysql and has a decent hope (use common sense) to work on
> postgresql. Once it's committed those who care about postgresql, if
> they so want to, can test and if there is a need, fix it.
> Prime example: http://drupal.org/node/146466 this is the most
> important patch we have currently as it makes Drupal search speedy and
> nice. And it is more or less on hold just because noone is sure
> whether the postgresql update works or not.
> Regards,
> Karoly Negyesi

More information about the development mailing list