Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: tiago_anastacio@yahoo.fr, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2019-04-02T00:41:26Z
Lists: 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
Commits
-
When restoring GUCs in parallel workers, show an error context.
- 3af7c64fe70c 12.1 landed
- 6737111a7ae1 11.6 landed
- 89a3cdb32a9e 10.11 landed
- fd5ffa425dfb 9.6.16 landed
- cdbb3921308e 9.5.20 landed
- 3c8c55dd5445 13.0 landed
-
Defer restoration of libraries in parallel workers.
- 6c3c9d418918 12.0 cited