mirror of
https://github.com/postgres/postgres.git
synced 2025-06-05 23:56:58 +03:00
Fix variable and type name in comment.
Kyotaro Horiguchi Discussion: https://www.postgresql.org/message-id/20170711.163441.241981736.horiguchi.kyotaro@lab.ntt.co.jp
This commit is contained in:
parent
66a3ea0711
commit
cf3e276853
@ -549,14 +549,14 @@ StandbyTimeoutHandler(void)
|
|||||||
* one transaction on one relation, and don't worry about lock queuing.
|
* one transaction on one relation, and don't worry about lock queuing.
|
||||||
*
|
*
|
||||||
* We keep a single dynamically expandible list of locks in local memory,
|
* We keep a single dynamically expandible list of locks in local memory,
|
||||||
* RelationLockList, so we can keep track of the various entries made by
|
* RecoveryLockList, so we can keep track of the various entries made by
|
||||||
* the Startup process's virtual xid in the shared lock table.
|
* the Startup process's virtual xid in the shared lock table.
|
||||||
*
|
*
|
||||||
* We record the lock against the top-level xid, rather than individual
|
* We record the lock against the top-level xid, rather than individual
|
||||||
* subtransaction xids. This means AccessExclusiveLocks held by aborted
|
* subtransaction xids. This means AccessExclusiveLocks held by aborted
|
||||||
* subtransactions are not released as early as possible on standbys.
|
* subtransactions are not released as early as possible on standbys.
|
||||||
*
|
*
|
||||||
* List elements use type xl_rel_lock, since the WAL record type exactly
|
* List elements use type xl_standby_lock, since the WAL record type exactly
|
||||||
* matches the information that we need to keep track of.
|
* matches the information that we need to keep track of.
|
||||||
*
|
*
|
||||||
* We use session locks rather than normal locks so we don't need
|
* We use session locks rather than normal locks so we don't need
|
||||||
|
Loading…
x
Reference in New Issue
Block a user