Commitf8cf524

committed

Fix bogus comment

1 parent56f8f96 commitf8cf524Copy full SHA for f8cf524

File tree

-3

lines changed

-3

lines changed

Lines changed: 4 additions & 3 deletions

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

Comments

(0)