From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andreas Seltenreich <seltenreich(at)gmx(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [sqlsmith] Parallel worker crash on seqscan |
Date: | 2016-11-21 17:00:37 |
Message-ID: | 22470.1479747637@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:
> On Mon, Nov 21, 2016 at 11:43 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> so what we've got is a case where a parameter computed by the FunctionScan
>> (in the master) would need to be passed into the parallel workers at
>> runtime. Do we have code for that at all? If so where is it?
> No, that's not supposed to happen.
OK, that makes this a planner failure: we should not have allowed this
query to become parallelized.
> Maybe it's checking the quals but not recursing into the tlist?
It seems like maybe searching for individual Params is the wrong thing.
Why are we allowing it to generate a parameterized Gather path at all?
Given the lack of any way to transmit runtime param values to the worker,
I can't see how that would ever work.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2016-11-21 17:04:34 | Re: delta relations in AFTER triggers |
Previous Message | Robert Haas | 2016-11-21 16:54:23 | Re: [sqlsmith] Parallel worker crash on seqscan |