aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2024-07-31 20:55:25 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2024-07-31 20:55:25 -0400
commitafbf32fa1aa87f710b623cbdf746c55b4799574e (patch)
tree10bb57940f0cd1bee68b3328bdccc6642ae84994 /src/tutorial
parent48536305370acd75c6264fcefec7fae7af8c5440 (diff)
downloadpostgresql-afbf32fa1aa87f710b623cbdf746c55b4799574e.tar.gz
postgresql-afbf32fa1aa87f710b623cbdf746c55b4799574e.zip
Revert "Allow parallel workers to cope with a newly-created session user ID."
This reverts commit 48536305370acd75c6264fcefec7fae7af8c5440. 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/tutorial')
0 files changed, 0 insertions, 0 deletions