git.postgresql.org Git - postgresql.git/commitdiff

git projects / postgresql.git / commitdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 4fc6b6e)
Fix comment in procarray.c.
2022年7月28日 05:56:20 +0000 (14:56 +0900)
2022年7月28日 05:56:20 +0000 (14:56 +0900)
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


diff --git a/src/backend/storage/ipc/procarray.c b/src/backend/storage/ipc/procarray.c
index dadaa958a84104e1ff36b002200e21322e1bc754..0555b02a8d95365f19dce5c5ddb13b8085b47218 100644 (file)
--- 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.
*/
This is the main PostgreSQL git repository.
RSS Atom

AltStyle によって変換されたページ (->オリジナル) /