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

Поиск
Список
Период
Сортировка
От ANASTACIO Tiago
Тема Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker
Дата
Msg-id 1831482307.24522245.1554199154256@mail.yahoo.com
обсуждение исходный текст
Ответ на Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker  (Thomas Munro <thomas.munro@gmail.com>)
Список pgsql-bugs
Дерево обсуждения
Thank you guys. I fixed the parameter and it worked.

A pity background worker are no more verbose (DEBUG5) than:

2019-04-02 09:42:38.993 GMT [17654] ERROR:  invalid name syntax

About Tracing
I used strace and grep background woker pid. But I didn't get that trace, which tool did you use ?


Le mardi 2 avril 2019 à 02:41:40 UTC+2, Peter Geoghegan <pg@bowt.ie> a écrit :


>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 по дате отправления:

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