Fix a typo in comment
Started by Yi Ding1 day ago2 messages
Hi Hackers,
Recently, I found a comment error in multixact.c. To address this, I've prepared a relevant patch.
For the details,please see the attached patch file.
Looking forward to your feedback.
Best regards,
--
Yi Ding
Attachments:
v1-0001-fix-a-comment-error.patchapplication/octet-stream; name=v1-0001-fix-a-comment-error.patch; x-cm-securityLevel=0; x-cm-securitylevel=0Download
From f1ea1ac748810e3f9eadd26a506fa04c9408f586 Mon Sep 17 00:00:00 2001
From: Yi Ding <dingyi_yale@163.com>
Date: Thu, 22 Jan 2026 17:43:40 +0800
Subject: [PATCH v1] fix a comment error
In the file multixact.c, there is a comment containing the phrase "it was already be set by the previous RecordNewMultiXact call," where the word "be" is redundant.
Author: Yi Ding <dingyi_yale@163.com>
---
src/backend/access/transam/multixact.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/backend/access/transam/multixact.c b/src/backend/access/transam/multixact.c
index 9585ffd..90ec87d 100644
--- a/src/backend/access/transam/multixact.c
+++ b/src/backend/access/transam/multixact.c
@@ -782,7 +782,7 @@ RecordNewMultiXact(MultiXactId multi, MultiXactOffset offset,
/*
* Set the starting offset of this multixid's members.
*
- * In the common case, it was already be set by the previous
+ * In the common case, it was already set by the previous
* RecordNewMultiXact call, as this was the next multixid of the previous
* multixid. But if multiple backends are generating multixids
* concurrently, we might race ahead and get called before the previous
--
1.8.3.1
