Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker
ANASTACIO Tiago <tiago_anastacio@yahoo.fr>
From: ANASTACIO Tiago <tiago_anastacio@yahoo.fr>
To: Thomas Munro <thomas.munro@gmail.com>, Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2019-04-02T09:59:14Z
Lists: 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 TracingI 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
Commits
-
When restoring GUCs in parallel workers, show an error context.
- 3af7c64fe70c 12.1 landed
- 6737111a7ae1 11.6 landed
- 89a3cdb32a9e 10.11 landed
- fd5ffa425dfb 9.6.16 landed
- cdbb3921308e 9.5.20 landed
- 3c8c55dd5445 13.0 landed
-
Defer restoration of libraries in parallel workers.
- 6c3c9d418918 12.0 cited