From: Robert Haas <rhaas@postgresql.org>
Date: Thu, 19 Dec 2019 14:24:44 +0000 (-0500)
Subject: Update neglected comment.
X-Git-Tag: REL_13_BETA1~996
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7cdcc747a9fe588f9e9b3a5d3feb650340093fb2;p=thirdparty%2Fpostgresql.git

Update neglected comment.

Commit d986d4e87f61c68f52c68ebc274960dc664b7b4e renamed a variable
but neglected to update the corresponding comment.

Amit Langote
---

diff --git a/src/backend/commands/trigger.c b/src/backend/commands/trigger.c
index faeea16d21a..99cb5bf557b 100644
--- a/src/backend/commands/trigger.c
+++ b/src/backend/commands/trigger.c
@@ -3033,8 +3033,8 @@ ExecBRUpdateTriggers(EState *estate, EPQState *epqstate,
 		/*
 		 * In READ COMMITTED isolation level it's possible that target tuple
 		 * was changed due to concurrent update.  In that case we have a raw
-		 * subplan output tuple in newSlot, and need to run it through the
-		 * junk filter to produce an insertable tuple.
+		 * subplan output tuple in epqslot_candidate, and need to run it
+		 * through the junk filter to produce an insertable tuple.
 		 *
 		 * Caution: more than likely, the passed-in slot is the same as the
 		 * junkfilter's output slot, so we are clobbering the original value