Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker
Date
Msg-id CAH2-Wzkif1R6imAhgcRv1cXqomYBDez9g1rKAhDixiEi7b2KOg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker
List pgsql-bugs
On Mon, Apr 1, 2019 at 5:33 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> Erm -- obviously that BEGIN was unnecessary and you see the error
> without it.  Anyway, the point I was making is that you don't get an
> error if you set it in postgresql.conf, but you do if you set it in
> other contexts, including the parallel worker startup sequence.  I
> wondered if this might have been a consequence of the parallel startup
> reordering that happened with commit 6c3c9d41, but nope --
> RestoreGUCState() was always run inside a transaction.

I wonder if this known issue is relevant here:

https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker
Next
From: David Rowley
Date:
Subject: Re: Parallel query execution introduces performance regressions