Re: problem with partitioned table and indexed json field - Mailing list pgsql-general

From Raphael Bauduin
Subject Re: problem with partitioned table and indexed json field
Date
Msg-id CAONrwUHJS_HTvMcFJ49n4DzeVVqsM8Lg97C4qs16kmm-V9Hm6w@mail.gmail.com
Whole thread Raw
In response to Re: problem with partitioned table and indexed json field  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general



On Thu, Nov 7, 2013 at 7:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
I wrote:
> It looks like the problem is we're building a MergeAppend plan and not
> getting the targetlist for the MergeAppend node right.

Found it --- simple oversight in building optimized min/max plans.
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

pgsql-general by date:

Previous
From: Francisco Olarte
Date:
Subject: Re: Breaking up a PostgreSQL COPY command into chunks?
Next
From: Victor Hooi
Date:
Subject: Re: Breaking up a PostgreSQL COPY command into chunks?