Fix typos referring to PGPROC
Japin Li Reviewed by Kyotaro Horiguchi Discussion: https://www.postgresql.org/message-id/MEYP282MB1669459813B36FB5EAA38434B6499@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
This commit is contained in:
parent
f66d997fd0
commit
08f8af983a
|
@ -198,7 +198,7 @@ parent. This maintains the invariant that child transactions have XIDs later
|
|||
than their parents, which is assumed in a number of places.
|
||||
|
||||
The subsidiary actions of obtaining a lock on the XID and entering it into
|
||||
pg_subtrans and PG_PROC are done at the time it is assigned.
|
||||
pg_subtrans and PGPROC are done at the time it is assigned.
|
||||
|
||||
A transaction that has no XID still needs to be identified for various
|
||||
purposes, notably holding locks. For this purpose we assign a "virtual
|
||||
|
|
|
@ -680,12 +680,12 @@ AssignTransactionId(TransactionState s)
|
|||
log_unknown_top = true;
|
||||
|
||||
/*
|
||||
* Generate a new FullTransactionId and record its xid in PG_PROC and
|
||||
* Generate a new FullTransactionId and record its xid in PGPROC and
|
||||
* pg_subtrans.
|
||||
*
|
||||
* NB: we must make the subtrans entry BEFORE the Xid appears anywhere in
|
||||
* shared storage other than PG_PROC; because if there's no room for it in
|
||||
* PG_PROC, the subtrans entry is needed to ensure that other backends see
|
||||
* shared storage other than PGPROC; because if there's no room for it in
|
||||
* PGPROC, the subtrans entry is needed to ensure that other backends see
|
||||
* the Xid as "running". See GetNewTransactionId.
|
||||
*/
|
||||
s->fullTransactionId = GetNewTransactionId(isSubXact);
|
||||
|
|
Loading…
Reference in New Issue