aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-08-15 21:05:21 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-08-15 21:05:59 -0400
commit226be4062865476d190701d6ac13082a0595121e (patch)
tree1d2ca5c094acff568766814b017fb854dfc70d15
parent3ea58216de4b26e27be8c6b23e44e275804542f2 (diff)
downloadpostgresql-226be4062865476d190701d6ac13082a0595121e.tar.gz
postgresql-226be4062865476d190701d6ac13082a0595121e.zip
Initialize replication_slot_catalog_xmin in procarray
Although not confirmed and probably rare, if the newly allocated memory is not already zero, this could possibly have caused some problems. Also reorder the initializations slightly so they match the order of the struct definition. Author: Wong, Yi Wen <yiwong@amazon.com> Reviewed-by: Masahiko Sawada <sawada.mshk@gmail.com>
-rw-r--r--src/backend/storage/ipc/procarray.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/backend/storage/ipc/procarray.c b/src/backend/storage/ipc/procarray.c
index ff96e2a86fe..ffa6180effd 100644
--- a/src/backend/storage/ipc/procarray.c
+++ b/src/backend/storage/ipc/procarray.c
@@ -237,13 +237,14 @@ CreateSharedProcArray(void)
*/
procArray->numProcs = 0;
procArray->maxProcs = PROCARRAY_MAXPROCS;
- procArray->replication_slot_xmin = InvalidTransactionId;
procArray->maxKnownAssignedXids = TOTAL_MAX_CACHED_SUBXIDS;
procArray->numKnownAssignedXids = 0;
procArray->tailKnownAssignedXids = 0;
procArray->headKnownAssignedXids = 0;
SpinLockInit(&procArray->known_assigned_xids_lck);
procArray->lastOverflowedXid = InvalidTransactionId;
+ procArray->replication_slot_xmin = InvalidTransactionId;
+ procArray->replication_slot_catalog_xmin = InvalidTransactionId;
}
allProcs = ProcGlobal->allProcs;