From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Revert "Allow parallel workers to cope with a newly-created sess |
Date: | 2024-08-01 00:57:14 |
Message-ID: | E1sZK82-0026z8-Qr@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Revert "Allow parallel workers to cope with a newly-created session user ID."
This reverts commit 5887dd4894db5ac1c6411615160555ac6e57e49b.
Some buildfarm animals are failing with "cannot change
"client_encoding" during a parallel operation". It looks like
assign_client_encoding is unhappy at being asked to roll back a
client_encoding setting after a parallel worker encounters a
failure. There must be more to it though: why didn't I see this
during local testing? In any case, it's clear that moving the
RestoreGUCState() call is not as side-effect-free as I thought.
Given that the bug f5f30c22e intended to fix has gone unreported
for years, it's not something that's urgent to fix; I'm not
willing to risk messing with it further with only days to our
next release wrap.
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/630b81d5cc00fa8bf1cb7e861a3778ed3080e621
Modified Files
--------------
src/backend/access/transam/parallel.c | 12 ++++--------
src/backend/commands/variable.c | 10 ++--------
src/test/regress/expected/select_parallel.out | 18 ------------------
src/test/regress/sql/select_parallel.sql | 9 ---------
4 files changed, 6 insertions(+), 43 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2024-08-01 03:21:36 | pgsql: Evaluate arguments of correlated SubPlans in the referencing Exp |
Previous Message | Jeff Davis | 2024-07-31 23:52:49 | pgsql: Add is_create parameter to RefreshMatviewByOid(). |