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 | 1034507245571a4a8e614299afe3f2e2ae858c27 (patch) | |
| tree | be9f199dfa1177519ab359236785b97051e08b92 /src/backend/executor/nodeLimit.c | |
| parent | 2e21e2857e5657b6867b337ddce5a22afce320c6 (diff) | |
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/nodeLimit.c')
0 files changed, 0 insertions, 0 deletions