rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Replace occurrences of InvalidXid with InvalidTransactionId 

While Xid is a known shortening of TransactionId, InvalidXid is not
defined in the code. Fix comments which mistakenly were using the
shorter version.

Author: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Discussion: https://postgr.es/m/CALj2ACUQzdigML868nV4cojfELPkEzNLNOk7b91Pho4JB90fng@mail.gmail.com
This commit is contained in:
Daniel Gustafsson 2021-10-04 10:31:01 +02:00
parent 8a4237908c
commit 941921b875
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/backend/access/heap/heapam.c
View File

@ -3589,9 +3589,9 @@ l2:
/* /*
* And also prepare an Xmax value for the new copy of the tuple. If there * And also prepare an Xmax value for the new copy of the tuple. If there
* was no xmax previously, or there was one but all lockers are now gone, * was no xmax previously, or there was one but all lockers are now gone,
* then use InvalidXid; otherwise, get the xmax from the old tuple. (In * then use InvalidTransactionId; otherwise, get the xmax from the old
* rare cases that might also be InvalidXid and yet not have the * tuple. (In rare cases that might also be InvalidTransactionId and yet
* HEAP_XMAX_INVALID bit set; that's fine.) * not have the HEAP_XMAX_INVALID bit set; that's fine.)
*/ */
if ((oldtup.t_data->t_infomask & HEAP_XMAX_INVALID) || if ((oldtup.t_data->t_infomask & HEAP_XMAX_INVALID) ||
HEAP_LOCKED_UPGRADED(oldtup.t_data->t_infomask) || HEAP_LOCKED_UPGRADED(oldtup.t_data->t_infomask) ||

6
src/backend/utils/time/snapmgr.c
View File

@ -919,9 +919,9 @@ xmin_cmp(const pairingheap_node *a, const pairingheap_node *b, void *arg)
/* /*
* SnapshotResetXmin * SnapshotResetXmin
* *
* If there are no more snapshots, we can reset our PGPROC->xmin to InvalidXid. * If there are no more snapshots, we can reset our PGPROC->xmin to
* Note we can do this without locking because we assume that storing an Xid * InvalidTransactionId. Note we can do this without locking because we assume
* is atomic. * that storing an Xid is atomic.
* *
* Even if there are some remaining snapshots, we may be able to advance our * Even if there are some remaining snapshots, we may be able to advance our
* PGPROC->xmin to some degree. This typically happens when a portal is * PGPROC->xmin to some degree. This typically happens when a portal is