diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2019-08-20 16:04:09 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2019-08-20 16:04:09 -0400 |
| commit | a923c426beafa1ae29ff2a229fe1b509e15f1ceb (patch) | |
| tree | 5e3453c0bcf9e7b301a2879dd668cac4dcdf81f2 | |
| parent | 15ae1a31b433cff340b14a11268a0c9746e4a19d (diff) | |
Fix bogus comment
Author: Alexander Lakhin
Discussion: https://postgr.es/m/20190819072244.GE18166@paquier.xyz
| -rw-r--r-- | src/backend/access/heap/heapam.c | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c index 3d1de722c8a..d00f4f23e5f 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3749,9 +3749,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 |