mirror of
https://git.postgresql.org/git/postgresql.git
synced 2026-02-19 04:46:59 +08:00
Allow parallel workers to cope with a newly-created session user ID.
Parallel workers failed after a sequence like BEGIN; CREATE USER foo; SET SESSION AUTHORIZATION foo; because check_session_authorization could not see the uncommitted pg_authid row for "foo". This is because we ran RestoreGUCState() in a separate transaction using an ordinary just-created snapshot. The same disease afflicts any other GUC that requires catalog lookups and isn't forgiving about the lookups failing. To fix, postpone RestoreGUCState() into the worker's main transaction after we've set up a snapshot duplicating the leader's. This affects check_transaction_isolation and check_transaction_deferrable, which think they should only run during transaction start. Make them act like check_transaction_read_only, which already knows it should silently accept the value when InitializingParallelWorker. This un-reverts commit f5f30c22e. The original plan was to back-patch that, but the fact that 0ae5b763e proved to be a pre-requisite shows that the subtle API change for GUC hooks might actually break some of them. The problem we're trying to fix seems not worth taking such a risk for in stable branches. Per bug #18545 from Andrey Rachitskiy. Discussion: https://postgr.es/m/18545-feba138862f19aaa@postgresql.org
This commit is contained in:
@ -511,3 +511,12 @@ SELECT 1 FROM tenk1_vw_sec
|
||||
WHERE (SELECT sum(f1) FROM int4_tbl WHERE f1 < unique1) < 100;
|
||||
|
||||
rollback;
|
||||
|
||||
-- test that a newly-created session role propagates to workers.
|
||||
begin;
|
||||
create role regress_parallel_worker;
|
||||
set session authorization regress_parallel_worker;
|
||||
select current_setting('session_authorization');
|
||||
set debug_parallel_query = 1;
|
||||
select current_setting('session_authorization');
|
||||
rollback;
|
||||
|
||||
Reference in New Issue
Block a user