Commitae04bf5

committed

Update transaction README for persistent multixacts

Multixacts are now maintained during recovery, but the README didn't getthe memo. Backpatch to 9.3, where the divergence was introduced.

1 parentd25367e commitae04bf5Copy full SHA for ae04bf5

File tree

-4

lines changed

-4

lines changed

Lines changed: 1 addition & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -840,10 +840,7 @@ parent transaction to complete.`
`840`	`840`
`841`	`841`	`Not all transactional behaviour is emulated, for example we do not insert`
`842`	`842`	`a transaction entry into the lock table, nor do we maintain the transaction`
`843`		`-stack in memory. Clog entries are made normally. Multixact is not maintained`
`844`		`-because its purpose is to record tuple level locks that an application has`
`845`		`-requested to prevent other tuple locks. Since tuple locks cannot be obtained at`
`846`		`-all, there is never any conflict and so there is no reason to update multixact.`
	`843`	`+stack in memory. Clog and multixact entries are made normally.`
`847`	`844`	`Subtrans is maintained during recovery but the details of the transaction`
`848`	`845`	`tree are ignored and all subtransactions reference the top-level TransactionId`
`849`	`846`	`directly. Since commit is atomic this provides correct lock wait behaviour`

Comments

(0)