mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix bogus comment

Browse Source 
Author: Alexander Lakhin
Discussion: https://postgr.es/m/20190819072244.GE18166@paquier.xyz
This commit is contained in:
Alvaro Herrera 2019-08-20 16:04:09 -04:00
parent 56f8f9624b
commit f8cf524da1
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/backend/access/heap/heapam.c
View File

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