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

From Thomas Munro
Subject Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker
Date
Msg-id CA+hUKGLftxFoLP6_qH6QnNPogTtOXp7cr+Bv7nV=CABRMWF_PQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker  (Daniel Gustafsson <dgustafsson@pivotal.io>)
Responses Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker  (Daniel Gustafsson <dgustafsson@pivotal.io>)
Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, Apr 11, 2019 at 8:59 PM Daniel Gustafsson
<dgustafsson@pivotal.io> wrote:
> > On 2 Apr 2019, at 21:54, Thomas Munro <thomas.munro@gmail.com> wrote:
> > psql: ERROR:  invalid name syntax
> > CONTEXT:  while setting parameter "default_text_search_config" to ""
> > parallel worker
>
> This makes it a lot better, but I wonder if it needs even more clarification to
> be easily understandable by users not familiar with how parallel workers are
> initiated.  I’m thinking we should add “during worker setup” or something
> similar to make it even clearer, albeit more verbose.

Thanks for the review.  How about this?

postgres=# set force_parallel_mode = on;
SET
postgres=# select 42;
psql: ERROR:  invalid name syntax
CONTEXT:  while setting parameter "default_text_search_config" to ""
in a parallel worker process
parallel worker

I think this is a bug and should be back-patched.  Objections?

--
Thomas Munro
https://enterprisedb.com

Attachment

pgsql-bugs by date:

Previous
From: Tobias Gierke
Date:
Subject: Re: BUG #15747: Help says 'application_name' property supports 64characters in a standard built but it's only 63
Next
From: Daniel Gustafsson
Date:
Subject: Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker