| From: | Steve Randall <srandall(at)s3(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Parallel Scan Bug: invalid attnum: 0 |
| Date: | 2016-11-10 16:50:02 |
| Message-ID: | CABVd52Xum9-92t9Q0=CHOkBTU=kKfUxyusioZ58Gn5Sn_o7ZHw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thank you.
On Thu, Nov 10, 2016 at 10:35 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
> > Immediate impression is that the logic for planning partial grouped
> > aggregation did not get the zero-sort-keys case right.
>
> Yeah: after flattening your view, the planner was left with GROUP BY
> 'S3'::character varying, which is a no-op, but it mistakenly inserted
> a no-op Sort into the plan to sort by that. One-liner fix is here
> if you need it right away:
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=
> 7defc3b97a31537547053946808a83e7234d1b61
>
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | avalon | 2016-11-10 18:39:35 | BUG #14418: PGAdmin 4 feature request/feedback |
| Previous Message | Tom Lane | 2016-11-10 16:35:42 | Re: Parallel Scan Bug: invalid attnum: 0 |