From d396606ebe9722baceabb156551169d83c85b8c8 Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Thu, 28 Jul 2022 14:56:20 +0900 Subject: [PATCH] Fix comment in procarray.c. Commit fea10a6434 renamed VariableCacheData.nextFullXid to nextXid. But commit dc7420c2c9 introduced the comment mentioning nextFullXid. This commit changes"nextFullXid" to "nextXid" in the comment. Author: Zhang Mingli Discussion: https://postgr.es/m/642BA615-4B28-4B0C-BDF6-4D33E366BCDF@gmail.com --- src/backend/storage/ipc/procarray.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/storage/ipc/procarray.c b/src/backend/storage/ipc/procarray.c index dadaa958a84..0555b02a8d9 100644 --- a/src/backend/storage/ipc/procarray.c +++ b/src/backend/storage/ipc/procarray.c @@ -4212,8 +4212,8 @@ GlobalVisTestIsRemovableXid(GlobalVisState *state, TransactionId xid) /* * Convert 32 bit argument to FullTransactionId. We can do so safely * because we know the xid has to, at the very least, be between - * [oldestXid, nextFullXid), i.e. within 2 billion of xid. To avoid taking - * a lock to determine either, we can just compare with + * [oldestXid, nextXid), i.e. within 2 billion of xid. To avoid taking a + * lock to determine either, we can just compare with * state->definitely_needed, which was based on those value at the time * the current snapshot was built. */