diff options
Diffstat (limited to 'src/backend/access/transam/README')
| -rw-r--r-- | src/backend/access/transam/README | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/access/transam/README b/src/backend/access/transam/README index 548ddbb4dd5..aabcbba49e8 100644 --- a/src/backend/access/transam/README +++ b/src/backend/access/transam/README @@ -791,10 +791,10 @@ parent transaction to complete. Not all transactional behaviour is emulated, for example we do not insert a transaction entry into the lock table, nor do we maintain the transaction -stack in memory. Clog entries are made normally. Multitrans is not maintained +stack in memory. Clog entries are made normally. Multixact is not maintained because its purpose is to record tuple level locks that an application has -requested to prevent write locks. Since write locks cannot be obtained at all, -there is never any conflict and so there is no reason to update multitrans. +requested to prevent other tuple locks. Since tuple locks cannot be obtained at +all, there is never any conflict and so there is no reason to update multixact. Subtrans is maintained during recovery but the details of the transaction tree are ignored and all subtransactions reference the top-level TransactionId directly. Since commit is atomic this provides correct lock wait behaviour |