Re: Standby accepts recovery_target_timeline setting?
Fujii Masao <masao.fujii@gmail.com>
From: Fujii Masao <masao.fujii@gmail.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, David Steele <david@pgmasters.net>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2019-09-29T16:36:55Z
Lists: pgsql-hackers
Attachments
- ignore-recovery-targets-in-crash-recovery.patch (application/octet-stream) patch
On Sun, Sep 29, 2019 at 6:08 AM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > > On 2019-09-28 19:45, Tom Lane wrote: > > Maybe I'm misunderstanding, but I think that rather than adding error > > checks that were not there before, the right path to fixing this is > > to cause these settings to be ignored if we're doing crash recovery. > > That makes sense to me. +1 > Something like this (untested)? Yes, but ArchiveRecoveryRequested should be checked instead of InArchiveRecovery, I think. Otherwise recovery targets would take effect when recovery.signal is missing but backup_label exists. In this case, InArchiveRecovery is set to true though ArchiveRecoveryRequested is false because recovery.signal is missing. With the attached patch, I checked that the steps that I described upthread didn't reproduce the issue. Regards, -- Fujii Masao
Commits
-
Make crash recovery ignore recovery_min_apply_delay setting.
- 03666dfa1817 12.1 landed
- 9b95a36be8be 13.0 landed
-
Make crash recovery ignore restore_command and recovery_end_command settings.
- fcf7f8d9242d 12.1 landed
- 20961ceaf042 13.0 landed
-
Make crash recovery ignore recovery target settings.
- 4af2ac3deeca 12.0 landed
- 7acf8a876b77 13.0 landed
-
doc: Further clarify how recovery target parameters are applied
- e04a53a6071d 13.0 landed
- a7e5ae53cbe7 12.0 landed
-
doc: Add timeline as valid recovery target in standby.signal documentation
- 775578a445bb 13.0 landed
- a37980d42824 12.0 landed