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 | 5a32fcdd7cac6668bbe2834c8af29a6103f8467b (patch) | |
| tree | 1a23359d9d1ea243ddb22ba21c8e9be9add7e8b1 /src | |
| parent | 7ffd4f3996e117e9aeb233f43ea6648cfe2abfd0 (diff) | |
| download | postgresql-5a32fcdd7cac6668bbe2834c8af29a6103f8467b.tar.gz postgresql-5a32fcdd7cac6668bbe2834c8af29a6103f8467b.zip | |
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 20871568f6e..784856ecf2c 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3465,9 +3465,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 |