| 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:32:45 |
| Message-ID: | CA+hUKGLdzBsa_SZajU8J9JDSHzdU6+LVq1g6bUsekiWBpjVDNQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Apr 2, 2019 at 1:24 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-04-02 00:41:26 | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |
| Previous Message | Thomas Munro | 2019-04-02 00:24:58 | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |