From: | Amit Kapila <amit(dot)kapila(at)enterprisedb(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ERROR: ORDER/GROUP BY expression not found in targetlist |
Date: | 2016-06-13 14:35:18 |
Message-ID: | CA+kptmA43Ga-BXziZ2o=eT8KO0b=aVQYPO7EOxGEDWm8bkwfdA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 13, 2016 at 7:17 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Mon, Jun 13, 2016 at 3:18 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:
> > In create_grouping_paths(), we are building partial_grouping_path and
same
> > is used for gather path and other grouping paths (for partial paths).
> > However, we don't use it for partial path list and sort path due to
which
> > path target for Sort path is different from what we have expected. Is
there
> > a problem in applying partial_grouping_path for partial pathlist?
> > Attached patch just does that and I don't see error with patch.
>
> It doesn't seem like a good idea to destructive modify
> input_rel->partial_pathlist. Applying the projection to each path
> before using it would probably be better.
>
Do you mean to have it when we generate a complete GroupAgg Path atop of
the cheapest partial path?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-06-13 14:41:02 | Re: ERROR: ORDER/GROUP BY expression not found in targetlist |
Previous Message | Amit Kapila | 2016-06-13 14:31:38 | Re: ERROR: ORDER/GROUP BY expression not found in targetlist |