| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | 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:41:26 |
| Message-ID: | CAH2-Wzkif1R6imAhgcRv1cXqomYBDez9g1rKAhDixiEi7b2KOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Apr 1, 2019 at 5:33 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-04-02 03:21:00 | Re: Parallel query execution introduces performance regressions |
| Previous Message | Thomas Munro | 2019-04-02 00:32:45 | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |