I wrote:
Andrew Gierth and...@tao11.riddles.org.uk writes:
Bruce == Bruce Momjian br...@momjian.us writes:
Bruce Uh, did this ever get addressed?
It did not.
It dropped off the radar screen (I think I'd assumed the patch would
appear in the next commitfest, which it didn't unless I missed
Bruce == Bruce Momjian br...@momjian.us writes:
Bruce Uh, did this ever get addressed?
It did not.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Andrew Gierth and...@tao11.riddles.org.uk writes:
Bruce == Bruce Momjian br...@momjian.us writes:
Bruce Uh, did this ever get addressed?
It did not.
It dropped off the radar screen (I think I'd assumed the patch would
appear in the next commitfest, which it didn't unless I missed something).
Uh, did this ever get addressed?
---
On Sun, Jul 6, 2014 at 08:56:00PM +0100, Andrew Gierth wrote:
Tom == Tom Lane t...@sss.pgh.pa.us writes:
I've experimented with the attached patch, which detects when this
Andrew Gierth and...@tao11.riddles.org.uk writes:
commit 807a40c5 fixed a bug in handling of (new in 9.2) functionality
of ScalarArrayOpExpr in btree index quals, forcing the results of
scans including such a qual to be treated as unordered (because the
order can in fact be wrong).
However,
Tom == Tom Lane t...@sss.pgh.pa.us writes:
I've experimented with the attached patch, which detects when this
situation might have occurred and does another pass to try and
build ordered scans without the SAOP condition. However, the
results may not be quite ideal, because at least in
