From: Alvaro Herrera Date: Tue, 20 Aug 2019 20:04:09 +0000 (-0400) Subject: Fix bogus comment X-Git-Tag: REL9_4_25~66 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=637dac906bf81e063f44afe46283e37dfe27019c;p=postgresql.git Fix bogus comment Author: Alexander Lakhin Discussion: https://postgr.es/m/20190819072244.GE18166@paquier.xyz --- diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c index 14e4ac2e2b8..38a7a2ca9ad 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3356,9 +3356,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