diff options
author | Andres Freund <andres@anarazel.de> | 2023-03-11 14:12:51 -0800 |
---|---|---|
committer | Andres Freund <andres@anarazel.de> | 2023-03-11 14:12:51 -0800 |
commit | 16327240da29b70e41a65d49212b31da9a94e177 (patch) | |
tree | 8531d28cff4dfac6fa406112c78a270448d9a874 /src/backend/executor/nodeProjectSet.c | |
parent | 4e633016abe9b82053aafb2fe9d3317add73f74d (diff) | |
download | postgresql-16327240da29b70e41a65d49212b31da9a94e177.tar.gz postgresql-16327240da29b70e41a65d49212b31da9a94e177.zip |
amcheck: Fix ordering bug in update_cached_xid_range()
The initialization order in update_cached_xid_range() was wrong, calling
FullTransactionIdFromXidAndCtx() before setting
->next_xid. FullTransactionIdFromXidAndCtx() uses ->next_xid.
In most situations this will not cause visible issues, because the next call
to update_cached_xid_range() will use a less wrong ->next_xid. It's rare that
xids advance fast enough for this to be a problem.
Found while adding more asserts to the 64bit xid infrastructure.
Reviewed-by: Mark Dilger <mark.dilger@enterprisedb.com>
Discussion: https://postgr.es/m/20230108002923.cyoser3ttmt63bfn@awork3.anarazel.de
Backpatch: 14-, where heapam verification was introduced
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions