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 | 44e9e34266efd42901bf7b12552f2033972d70b7 (patch) | |
| tree | 30e83cda43e143378d072e57519c9ef1766007da /src/backend/utils/adt/tsvector_op.c | |
| parent | 438e6b7240905c8055f9e221187f2ac818876169 (diff) | |
| download | postgresql-44e9e34266efd42901bf7b12552f2033972d70b7.tar.gz postgresql-44e9e34266efd42901bf7b12552f2033972d70b7.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/utils/adt/tsvector_op.c')
0 files changed, 0 insertions, 0 deletions