diff options
| author | Thomas Munro <tmunro@postgresql.org> | 2019-07-15 17:03:46 +1200 |
|---|---|---|
| committer | Thomas Munro <tmunro@postgresql.org> | 2019-07-15 17:04:29 +1200 |
| commit | 67b9b3ca328392f9afc4e66fe03564f5fc87feff (patch) | |
| tree | 4297fdc8925b8d36fc413e03cbce0ac79f5ca094 /src/backend/utils/adt/partitionfuncs.c | |
| parent | 5925e5549890416bcf588334d9d0bc99f8ad6c7f (diff) | |
| download | postgresql-67b9b3ca328392f9afc4e66fe03564f5fc87feff.tar.gz postgresql-67b9b3ca328392f9afc4e66fe03564f5fc87feff.zip | |
Provide XLogRecGetFullXid().
In order to be able to work with FullTransactionId values during replay
without increasing the size of the WAL, infer the epoch. In general we
can't do that safely, but during replay we can because we know that
nextFullXid can't advance concurrently.
Prevent frontend code from seeing this new function, due to the above
restriction. Perhaps in future it will be possible to extract the value
entirely from independent WAL records, and then this restriction can be
lifted.
Author: Thomas Munro, based on earlier code from Andres Freund
Discussion: https://postgr.es/m/CA%2BhUKG%2BmLmuDjMi6o1dxkKvGRL56Y2Rz%2BiXAcrZV03G9ZuFQ8Q%40mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/partitionfuncs.c')
0 files changed, 0 insertions, 0 deletions