From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | tiago_anastacio(at)yahoo(dot)fr, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |
Date: | 2019-04-02 00:24:58 |
Message-ID: | CA+hUKGKJ-amPMuwFhgc5T6UH=Wcn3CG3gmowmkYqTo2WsQJM4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Apr 2, 2019 at 10:59 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> On Tue, Apr 2, 2019 at 12:24 AM PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
> > default_text_search_config = '' #default 'pg_catalog.simple'
>
> That causes problems for parallel workers. The stack looks like this:
> Why is the empty string acceptable to the master but not with
> RestoreGUCState() in a parallel worker?
Because check_TSCurrentConfig() only reports and error if there is an
active transaction. So you can see this without parallelism like
this:
postgres=# begin;
BEGIN
postgres=# set default_text_search_config = '';
psql: ERROR: invalid name syntax
I think the short term answer is that you need a better value for
default_text_search_config. It's unfortunate that this error is
normally hidden, but then jumps out with an incomprehensible message
when you run a parallel query. Perhaps someone who knows more about
TS than me could comment on whether this should be considered a bug?
--
Thomas Munro
https://enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2019-04-02 00:32:45 | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |
Previous Message | Thomas Munro | 2019-04-01 21:59:48 | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |