On Monday, July 28, 2025, Jacob Champion <jacob.champ...@enterprisedb.com> wrote: > > > Recovery will abort and the server will not start up if any of the > following events occur: the command is terminated by a signal other > than SIGTERM (which is used as part of a database server shutdown); > the command returns an exit status greater than 125; or the shell > returns an error, such as "command not found". >
I don’t understand calling out sigterm as an exception, the same abort-and-shutdown action happens there too. And in any case signals are turned into exit status values anyway so naming them specifically seems redundant. The “Command not found” error is defined by POSIX as exit status 127 making its specification redundant with > 125 “The server interprets the exit status per POSIX conventions: 0 for success, and any value between 1-125 to gracefully handle the case where a file name is supplied that does not exist, or exhibits a temporary failure during processing. All other exit status values are considered fatal, causing recovery to be aborted and the server stopped.” David J.
