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

From Jean-Christophe Arnu
Subject Re: restore_command return code behaviour
Date
Msg-id CAHZmTm2359S1cnQS2MJkAXopLrP2faQnph0kfVbAmDPg1Z3a3g@mail.gmail.com
Whole thread Raw
In response to Re: restore_command return code behaviour  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers

Le lun. 4 août 2025, 04:45, David G. Johnston <david.g.johnston@gmail.com> a écrit :

How about:

Recovery will abort and the server will not start up upon any of the following:
the shell is unable to execute the command (due to it not being found or executable),
the command returns an exit status greater than 125, or a non-SIGTERM signal
terminates the shell process.  SIGTERM allows a clean shutdown to happen, if there is one.


Mostly just changing the order a bit but goes from most immediate when making a change (bad command written into the GUC) to least immediate or surprising (SIGTERM).  The other two flow from there.


I agree. I like this concise way to explain the different cases.

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: GB18030-2022 Support in PostgreSQL
Next
From: Álvaro Herrera
Date:
Subject: don't include tableam.h in nbtree.h