mirror of
https://github.com/postgres/postgres.git
synced 2025-07-07 00:36:50 +03:00
Add subtransaction handling for table synchronization workers.
Since the old logic was completely unaware of subtransactions, a change made in a subsequently-aborted subtransaction would still cause workers to be stopped at toplevel transaction commit. Fix that by managing a stack of worker lists rather than just one. Amit Khandekar and Robert Haas Discussion: http://postgr.es/m/CAJ3gD9eaG_mWqiOTA2LfAug-VRNn1hrhf50Xi1YroxL37QkZNg@mail.gmail.com
This commit is contained in:
@ -4637,6 +4637,7 @@ CommitSubTransaction(void)
|
||||
AtEOSubXact_HashTables(true, s->nestingLevel);
|
||||
AtEOSubXact_PgStat(true, s->nestingLevel);
|
||||
AtSubCommit_Snapshot(s->nestingLevel);
|
||||
AtEOSubXact_ApplyLauncher(true, s->nestingLevel);
|
||||
|
||||
/*
|
||||
* We need to restore the upper transaction's read-only state, in case the
|
||||
@ -4790,6 +4791,7 @@ AbortSubTransaction(void)
|
||||
AtEOSubXact_HashTables(false, s->nestingLevel);
|
||||
AtEOSubXact_PgStat(false, s->nestingLevel);
|
||||
AtSubAbort_Snapshot(s->nestingLevel);
|
||||
AtEOSubXact_ApplyLauncher(false, s->nestingLevel);
|
||||
}
|
||||
|
||||
/*
|
||||
|
Reference in New Issue
Block a user