From: | Raphael Bauduin <rblists(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: problem with partitioned table and indexed json field |
Date: | 2013-11-08 08:03:19 |
Message-ID: | CAONrwUHJS_HTvMcFJ49n4DzeVVqsM8Lg97C4qs16kmm-V9Hm6w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Nov 7, 2013 at 7:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Hooi | 2013-11-08 08:28:29 | Re: Breaking up a PostgreSQL COPY command into chunks? |
Previous Message | Francisco Olarte | 2013-11-08 07:36:00 | Re: Breaking up a PostgreSQL COPY command into chunks? |