Re: Processing long AND/OR lists - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: Processing long AND/OR lists
Date
Msg-id CABwTF4V9rsjiBWE+87pK83Mmm7ACdrG7sZ08RQ-4qYMe8jvhbw@mail.gmail.com
Whole thread Raw
In response to Re: Processing long AND/OR lists  (Christopher Browne <cbbrowne@gmail.com>)
Responses Re: Processing long AND/OR lists  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Mon, May 27, 2013 at 10:32 AM, Christopher Browne <cbbrowne@gmail.com> wrote:
On Mon, May 27, 2013 at 1:42 AM, Gurjeet Singh <gurjeet@singh.im> wrote:
 
Joking about "640K" aside, it doesn't seem reasonable to expect a truly enormous query as is generated by the broken forms of this logic to turn out happily.  I'd rather fix Slony (as done in the above patch).

Yes, by all means, fix the application, but that doesn't preclude the argument that the database should be a bit more smarter and efficient, especially if it is easy to do.

Agreed, it seems like a fine idea to have the database support such queries, as this eases coping with applications that might be more difficult to get fixed.

Seeing no more objections to it, I am going to add this patch to the commitfest. Attached is updated patch against latest master; it's the same as the previous version, except that that the patch now includes a fix for the failing test case as well.

Best regards,
--
Gurjeet Singh

http://gurjeet.singh.im/

EnterpriseDB Inc.
Attachment

pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Statement timeout logging
Next
From: Robert Haas
Date:
Subject: Re: RFC: ExecNodeExtender