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