Robert Haas <robertmh...@gmail.com> writes: > On Mon, Nov 21, 2016 at 12:00 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> 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.
> Hmm, so you're thinking it could be the job of generate_gather_paths() > to make sure we don't do that? Actually, the Gather path *isn't* parameterized. The problem here is that we're planning an unflattened subquery, and the only thing that is parallel-unsafe is that there is an outer Param in its toplevel tlist, and we're somehow deciding that we can stick that unsafe tlist into (and beneath) the Gather node. So something rotten in that area, but I've not quite found it yet. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers