Remove recovery.signal at recovery end when both signal files are present. When both standby.signal and recovery.signal are present, standby.signal takes precedence and the server runs in standby mode. Previously, in this case, recovery.signal was not removed at the end of standby mode (i.e., on promotion) or at the end of archive recovery, while standby.signal was removed. As a result, a leftover recovery.signal could cause a subsequent restart to enter archive recovery unexpectedly, potentially preventing the server from starting. This behavior was surprising and confusing to users.
This commit fixes the issue by updating the recovery code to remove recovery.signal alongside standby.signal when both files are present and recovery completes. Because this code path is particularly sensitive and changes in recovery behavior can be risky for stable branches, this change is applied only to the master branch. Reported-by: Nikolay Samokhvalov <[email protected]> Author: Fujii Masao <[email protected]> Reviewed-by: Michael Paquier <[email protected]> Reviewed-by: David Steele <[email protected]> Discussion: https://postgr.es/m/cam527d8pvaqflt_ndtxe19f-xpdzui861882l0rly3yihqb...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/351265a6c7fd15737e4b68cada778728fc325a8b Modified Files -------------- src/backend/access/transam/xlogrecovery.c | 10 ++++++---- src/test/recovery/t/002_archiving.pl | 18 +++++++++++++++++- 2 files changed, 23 insertions(+), 5 deletions(-)
