From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andreas Seltenreich <seltenreich(at)gmx(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [sqlsmith] Failed assertion in parallel worker (ExecInitSubPlan) |
Date: | 2016-05-12 17:54:38 |
Message-ID: | CA+Tgmob-rT9AMR9aCeGLg_B-grJCmy8VJj=uCSXT607AhVnOtw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 12, 2016 at 11:48 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I could be wrong, but I thought that the target list for an expression
>> would always contain only Vars at this stage. Non-default tlists get
>> injected at the end of scan/join planning. Am I wrong?
>
> Target list for a relation, you mean? See relation.h:
>
> * reltarget - Default Path output tlist for this rel; normally contains
> * Var and PlaceHolderVar nodes for the values we need to
> * output from this relation.
> * List is in no particular order, but all rels of an
> * appendrel set must use corresponding orders.
> * NOTE: in an appendrel child relation, may contain
> * arbitrary expressions pulled up from a subquery!
Err, wow. That makes my head hurt. Can you explain why this case
only arises for appendrel children, and not for plain rels?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-12 18:07:29 | Re: [sqlsmith] Failed assertion in parallel worker (ExecInitSubPlan) |
Previous Message | Andres Freund | 2016-05-12 15:58:45 | Re: Perf Benchmarking and regression. |