diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2023-01-19 12:23:20 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2023-01-19 12:23:20 -0500 |
| commit | 1b9a0b96a8701ddcd147836241f89d616772d332 (patch) | |
| tree | 33cba6b956527eb7d7c029ada418f28048503eeb /src/backend/executor/nodeRecursiveunion.c | |
| parent | fed4e92f3bfd4dfbbee472fb4b0b86d9b9100a3c (diff) | |
| download | postgresql-1b9a0b96a8701ddcd147836241f89d616772d332.tar.gz postgresql-1b9a0b96a8701ddcd147836241f89d616772d332.zip | |
Log the correct ending timestamp in recovery_target_xid mode.
When ending recovery based on recovery_target_xid matching with
recovery_target_inclusive = off, we printed an incorrect timestamp
(always 2000-01-01) in the "recovery stopping before ... transaction"
log message. This is a consequence of sloppy refactoring in
c945af80c: the code to fetch recordXtime out of the commit/abort
record used to be executed unconditionally, but it was changed
to get called only in the RECOVERY_TARGET_TIME case. We need only
flip the order of operations to restore the intended behavior.
Per report from Torsten Förtsch. Back-patch to all supported
branches.
Discussion: https://postgr.es/m/CAKkG4_kUevPqbmyOfLajx7opAQk6Cvwkvx0HRcFjSPfRPTXanA@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeRecursiveunion.c')
0 files changed, 0 insertions, 0 deletions