forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commitabe2033
committed
Log the correct ending timestamp in recovery_target_xid mode.
When ending recovery based on recovery_target_xid matching withrecovery_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 inc945af8: the code to fetch recordXtime out of the commit/abortrecord used to be executed unconditionally, but it was changedto get called only in the RECOVERY_TARGET_TIME case. We need onlyflip the order of operations to restore the intended behavior.Per report from Torsten Förtsch. Back-patch to all supportedbranches.Discussion:https://postgr.es/m/CAKkG4_kUevPqbmyOfLajx7opAQk6Cvwkvx0HRcFjSPfRPTXanA@mail.gmail.com1 parent49e3a5e commitabe2033
1 file changed
+7
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2544 | 2544 | | |
2545 | 2545 | | |
2546 | 2546 | | |
2547 | | - | |
2548 | | - | |
| 2547 | + | |
| 2548 | + | |
| 2549 | + | |
| 2550 | + | |
| 2551 | + | |
| 2552 | + | |
| 2553 | + | |
2549 | 2554 | | |
2550 | 2555 | | |
2551 | 2556 | | |
| |||
0 commit comments
Comments
(0)