aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2022-11-25 09:25:50 +0530
committerAmit Kapila <akapila@postgresql.org>2022-11-25 09:25:50 +0530
commit9f2cc1a73ccf84c24dc4c386721b3bb73757dc24 (patch)
tree56f297b8f502bf85c0c050b73db367e4fde01809
parent8e7c86785a11cd3e56f895b8e2a489546c36a350 (diff)
downloadpostgresql-9f2cc1a73ccf84c24dc4c386721b3bb73757dc24.tar.gz
postgresql-9f2cc1a73ccf84c24dc4c386721b3bb73757dc24.zip
Fix uninitialized access to InitialRunningXacts during decoding.
In commit 272248a0c, we introduced an InitialRunningXacts array to remember transactions and subtransactions that were running when the xl_running_xacts record that we decoded was written. This array was allocated in the snapshot builder memory context after we restore serialized snapshot but we forgot to reset the array while freeing the builder memory context. So, the next time when we start decoding in the same session where we don't restore any serialized snapshot, we ended up using the uninitialized array and that can lead to unpredictable behavior. This problem doesn't exist in HEAD as instead of using InitialRunningXacts, we added the list of transaction IDs and sub-transaction IDs, that have modified catalogs and are running during snapshot serialization, to the serialized snapshot (see commit 7f13ac8123). Reported-by: Maxim Orlov Author: Masahiko Sawada Reviewed-by: Amit Kapila, Maxim Orlov Backpatch-through: 11 Discussion: https://postgr.es/m/CACG=ezZoz_KG+Ryh9MrU_g5e0HiVoHocEvqFF=NRrhrwKmEQJQ@mail.gmail.com
-rw-r--r--src/backend/replication/logical/snapbuild.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/src/backend/replication/logical/snapbuild.c b/src/backend/replication/logical/snapbuild.c
index 977440b9420..b5b018e6971 100644
--- a/src/backend/replication/logical/snapbuild.c
+++ b/src/backend/replication/logical/snapbuild.c
@@ -343,6 +343,9 @@ AllocateSnapshotBuilder(ReorderBuffer *reorder,
MemoryContextSwitchTo(oldcontext);
+ /* The initial running transactions array must be empty. */
+ Assert(NInitialRunningXacts == 0 && InitialRunningXacts == NULL);
+
return builder;
}
@@ -363,6 +366,10 @@ FreeSnapshotBuilder(SnapBuild *builder)
/* other resources are deallocated via memory context reset */
MemoryContextDelete(context);
+
+ /* InitialRunningXacts is freed along with the context */
+ NInitialRunningXacts = 0;
+ InitialRunningXacts = NULL;
}
/*