| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sorting a union over inheritance vs pathkeys |
| Date: | 2014-06-26 12:04:48 |
| Message-ID: | FAFB5A87-B574-45E1-83C3-30900227BD4F@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jun 25, 2014, at 22:14, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
>> Michael Glaesemann <grzm(at)seespotcode(dot)net> writes:
>>> -- ERROR: could not find pathkey item to sort
>
>> Hm ... I can reproduce that in 9.3 but it seems fine in 9.4 and HEAD.
>> Don't know what's going on exactly.
>
> Interesting --- it appears that commit
> a87c729153e372f3731689a7be007bc2b53f1410 is why it works in 9.4. I had
> thought that was just improving plan quality, but it seems to also prevent
> this problem. I guess we'd better back-patch it.
Thanks, Tom!
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-06-26 12:10:55 | bad estimation together with large work_mem generates terrible slow hash joins |
| Previous Message | Petr Jelinek | 2014-06-26 11:27:26 | Re: Set new system identifier using pg_resetxlog |