postgres.git / summary / log / commit / refs
commit a1fc50672c4b410f6a75db1efe807efeaccf571c
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: Sat Mar 19 18:31:38 2022 +0000
First released in: 15.0
Fix an outdated and grammatically wrong comment
Authored by Amit Langote and myself independently
Discussion: https://postgr.es/m/CA+HiwqGCjcH0gG-=tM7hhP7TEDmzrHMHJbPGSHtHgFmx9mnFkg@mail.gmail.com
src/backend/executor/nodeModifyTable.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/backend/executor/nodeModifyTable.c b/src/backend/executor/nodeModifyTable.c
index 6239abae904..babf26810b7 100644
--- a/src/backend/executor/nodeModifyTable.c
+++ b/src/backend/executor/nodeModifyTable.c
@@ -1517,9 +1517,9 @@ ldelete:;
* for the caller.
*
* False is returned if the tuple we're trying to move is found to have been
- * concurrently updated. In that case, the caller must to check if the
- * updated tuple that's returned in *retry_slot still needs to be re-routed,
- * and call this function again or perform a regular update accordingly.
+ * concurrently updated. In that case, the caller must check if the updated
+ * tuple (in updateCxt->cpUpdateRetrySlot) still needs to be re-routed, and
+ * call this function again or perform a regular update accordingly.
*/
static bool
ExecCrossPartitionUpdate(ModifyTableContext *context,
[parent: eb8399cf1f3d]