Re: restore_command return code behaviour - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: restore_command return code behaviour
Date
Msg-id CAOYmi+nAPX5fBxcS3=ba439bBUN6eaZxi569d9kPqZfZ1Wk1sQ@mail.gmail.com
Whole thread Raw
In response to restore_command return code behaviour  (Jean-Christophe Arnu <jcarnu@gmail.com>)
Responses Re: restore_command return code behaviour
List pgsql-hackers
On Thu, Jul 24, 2025 at 2:18 PM Jean-Christophe Arnu <jcarnu@gmail.com> wrote:
> Could we perhaps improve the documentation by stating that return codes over 125 or (at least) 128 will lead to the
servernot starting? 
>
> This may help people better understand the behaviour of the restore_command and quickly solve these kinds of issues
withouthaving to examine the source code. 
>
> If you agree, we can suggest a patch for the documentation.

If you've tripped over it, I think we should consider a docs patch.

To confirm -- you're happy with the behavior as-is?

--Jacob



pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: More protocol.h replacements this time into walsender.c
Next
From: "Joel Jacobson"
Date:
Subject: Re: Interrupts vs signals