Commit39c2056

committed

Fix bogus comment

1 parent93dcec9 commit39c2056Copy full SHA for 39c2056

File tree

-3

lines changed

-3

lines changed

Lines changed: 4 additions & 3 deletions

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

Comments

(0)