Horton

Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: tiago_anastacio@yahoo.fr, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2019-04-02T00:32:45Z
Lists: pgsql-bugs 
On Tue, Apr 2, 2019 at 1:24 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> postgres=# begin;
> BEGIN
> postgres=# set default_text_search_config = '';
> psql: ERROR:  invalid name syntax

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.

-- 
Thomas Munro
https://enterprisedb.com

Commits

  1. When restoring GUCs in parallel workers, show an error context.

  2. Defer restoration of libraries in parallel workers.