postgrespro.git / summary / log / commit / refs

commit    7cdcc747a9fe588f9e9b3a5d3feb650340093fb2
Author:   Robert Haas <rhaas@postgresql.org>
Date:     Thu Dec 19 14:24:44 2019 +0000

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


 src/backend/commands/trigger.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/backend/commands/trigger.c b/src/backend/commands/trigger.c
index faeea16d21..99cb5bf557 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


[parent: 303640199d04]