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

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker
Дата
Msg-id CAH2-Wzkif1R6imAhgcRv1cXqomYBDez9g1rKAhDixiEi7b2KOg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker  (Thomas Munro <thomas.munro@gmail.com>)
Ответы Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker  (ANASTACIO Tiago <tiago_anastacio@yahoo.fr>)
Список pgsql-bugs
On Mon, Apr 1, 2019 at 5:33 PM Thomas Munro <thomas.munro@gmail.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



В списке pgsql-bugs по дате отправления:

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker
Следующее
От: David Rowley
Дата:
Сообщение: Re: Parallel query execution introduces performance regressions