Commita923c42

committed

Fix bogus comment

1 parent15ae1a3 commita923c42Copy full SHA for a923c42

File tree

-3

lines changed

-3

lines changed

Lines changed: 4 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -3749,9 +3749,10 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,`
`3749`	`3749`	`* Note that the multixact may not be done by now. It could have`
`3750`	`3750`	`* surviving members; our own xact or other subxacts of this`
`3751`	`3751`	`* backend, and also any other concurrent transaction that locked`
`3752`		`- * the tuple with KeyShare if we only got TupleLockUpdate. If`
`3753`		`- * this is the case, we have to be careful to mark the updated`
`3754`		`- * tuple with the surviving members in Xmax.`
	`3752`	`+ * the tuple with LockTupleKeyShare if we only got`
	`3753`	`+ * LockTupleNoKeyExclusive. If this is the case, we have to be`
	`3754`	`+ * careful to mark the updated tuple with the surviving members in`
	`3755`	`+ * Xmax.`
`3755`	`3756`	`*`
`3756`	`3757`	`* Note that there could have been another update in the`
`3757`	`3758`	`* MultiXact. In that case, we need to check whether it committed`

Comments

(0)