Commit637dac9

committed

Fix bogus comment

1 parentfbfa2bb commit637dac9Copy full SHA for 637dac9

File tree

-3

lines changed

-3

lines changed

Lines changed: 4 additions & 3 deletions

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

Comments

(0)