| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila(at)enterprisedb(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 21:50:33 |
| Message-ID: | 23011.1465854633@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Oh, one other thing about this: I'm not going to try to defend
> whatever confusion between subplans and subqueries appears in that
> comment, but prior to upper planner pathification I think we were dead
> in the water here anyway, because the subquery was going to output a
> finished plan, not a list of paths. Since finished plans aren't
> labeled as to parallel-safety, we'd have to conservatively assume that
> the finished plan we got back might not be parallel-safe. Now that
> we're using the path representation throughout, we can do better.
Well, if that were still the state of affairs, we could certainly consider
adding a parallel_safe flag to Plans as well as Paths. But as you say,
it's moot now.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-06-13 21:51:53 | Re: [sqlsmith] Failed assertion in postgres_fdw/deparse.c:1116 |
| Previous Message | Tom Lane | 2016-06-13 21:46:41 | Re: ERROR: ORDER/GROUP BY expression not found in targetlist |