diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2024-07-31 20:53:33 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2024-07-31 20:57:00 -0400 |
commit | e6a9637488e2673efb87f8ead657789e9889fb17 (patch) | |
tree | 99b5428f8aafd3a9008ec802b534c32c338dda1f /src/backend/tcop/postgres.c | |
parent | ca2eea3ac89a4ea16ab069cb681510d05de5285f (diff) | |
download | postgresql-e6a9637488e2673efb87f8ead657789e9889fb17.tar.gz postgresql-e6a9637488e2673efb87f8ead657789e9889fb17.zip |
Revert "Allow parallel workers to cope with a newly-created session user ID."
This reverts commit f5f30c22ed69fb37b896c4d4546b2ab823c3fd61.
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.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions