postgrespro.git / summary / log / commit / refs

commit    f8cf524da15ec4d8fad26aeff44af9928d30eb3d
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Tue Aug 20 20:04:09 2019 +0000

    Fix bogus comment
    
    Author: Alexander Lakhin
    Discussion: https://postgr.es/m/20190819072244.GE18166@paquier.xyz


 src/backend/access/heap/heapam.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c
index 718f07f4f6..cb811d345a 100644
--- a/src/backend/access/heap/heapam.c
+++ b/src/backend/access/heap/heapam.c
@@ -3165,9 +3165,10 @@ l2:
 			 * Note that the multixact may not be done by now.  It could have
 			 * surviving members; our own xact or other subxacts of this
 			 * backend, and also any other concurrent transaction that locked
-			 * the tuple with KeyShare if we only got TupleLockUpdate.  If
-			 * this is the case, we have to be careful to mark the updated
-			 * tuple with the surviving members in Xmax.
+			 * the tuple with LockTupleKeyShare if we only got
+			 * LockTupleNoKeyExclusive.  If this is the case, we have to be
+			 * careful to mark the updated tuple with the surviving members in
+			 * Xmax.
 			 *
 			 * Note that there could have been another update in the
 			 * MultiXact. In that case, we need to check whether it committed


[parent: 56f8f9624ba0]