On Thu, Nov 7, 2013 at 7:24 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Wow, the patch is available thes same day I supplied the steps to reproduce the bug! I don't think it's possible to be faster :-)
Thanks a alot!
Raph
I wrote:Found it --- simple oversight in building optimized min/max plans.
> It looks like the problem is we're building a MergeAppend plan and not
> getting the targetlist for the MergeAppend node right.
If you need a patch now, see
http://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=5d0731da521f090f80ea39529fe274ac6d6bffa1
Wow, the patch is available thes same day I supplied the steps to reproduce the bug! I don't think it's possible to be faster :-)
Thanks a alot!
Raph
regards, tom lane
--
Web database: http://www.myowndb.com
Free Software Developers Meeting: http://www.fosdem.org
