Horton
Menu

Re: recovery.signal not cleaned up when both signal files are present

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: David Steele <david@pgbackrest.org>
Cc: Fujii Masao <masao.fujii@gmail.com>, Nikolay Samokhvalov <nik@postgres.ai>, pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-02-13T02:31:12Z
Lists: pgsql-hackers 
On Fri, Feb 13, 2026 at 12:55:15AM +0000, David Steele wrote:
> Reluctantly I have to agree to not back patch this. I'm not sure how this
> change would break existing recovery processes but experience tells me that
> it probably would.
> 
> Instead -- I wonder if we could add a warning in the back branches?

I am not convinced that going down to that is really necessary based
on the lack of complaints, and it could even be qualified as
disturbing for existing cases as well?  Let's leave that as a
HEAD-only change.
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove recovery.signal at recovery end when both signal files are present.