Re: aborting startup due to startup process failure - Mailing list pgsql-admin

From Tom Lane
Subject Re: aborting startup due to startup process failure
Date
Msg-id 3048.1183083368@sss.pgh.pa.us
Whole thread Raw
In response to aborting startup due to startup process failure  ("George Wilk" <gwilk@ellacoya.com>)
Responses Re: aborting startup due to startup process failure  ("George Wilk" <gwilk@ellacoya.com>)
List pgsql-admin
"George Wilk" <gwilk@ellacoya.com> writes:
> I am running a warm standby server, which executes the following command in
> a recovery mode:
> [ when done: ]
>   exit 133

Did you pick that number out of a hat?  Postgres thinks it means that
the recovery command died horribly, and abandons the recovery as a
safety measure.  (Per Single Unix Spec, this exit code from a shell
script would ordinarily mean that some program the shell called
died with a signal 5.)

Use "exit 1" or some low number like that to signal ordinary failure
to find the requested xlog file.  Numbers larger than about 125 mean
catastrophic failure of the recovery command.

            regards, tom lane

pgsql-admin by date:

Previous
From: Tom Arthurs
Date:
Subject: Re: aborting startup due to startup process failure
Next
From: "George Wilk"
Date:
Subject: Re: aborting startup due to startup process failure