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 | 516613d4a16a8e360b9e07d2fcbbdec96efb8cce (patch) | |
| tree | 4f8bd542687f37fa91cf7eec8724488b561621d1 /src | |
| parent | 3399b345f1d4047b7c2777946bdd05b1938ed6d1 (diff) | |
Fix bogus comment
Author: Alexander Lakhin
Discussion: https://postgr.es/m/20190819072244.GE18166@paquier.xyz
Diffstat (limited to 'src')
| -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 0c9be0f626e..f2f7396c006 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3698,9 +3698,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 |