Re: Shutting down a warm standby database in 8.2beta3 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Shutting down a warm standby database in 8.2beta3
Date
Msg-id 3741.1164225783@sss.pgh.pa.us
Whole thread Raw
In response to Re: Shutting down a warm standby database in 8.2beta3  (Stephen Harris <lists@spuddy.org>)
Responses Re: Shutting down a warm standby database in 8.2beta3  (Stephen Harris <lists@spuddy.org>)
List pgsql-hackers
Stephen Harris <lists@spuddy.org> writes:
> We can see that the sleep process got it!
>   /export/home/swharris/rr[37]: 29537 Quit(coredump)
> And my script detects the trigger file
>   Wed Nov 22 13:43:51 EST 2006: End of recovery trigger file found

> Now database recovery appears to continue as normal; the postgres
> recovery processes are still running, despite having received SIGQUIT

Well, sure, because system() will have ignored the SIGQUIT.  You have to
make the shell script return an abort code rather than exit(1) or
whatever it's doing in this case.  (I've tested that CVS HEAD does the
right thing when the script is just a straight invocation of cp.  But
if the script is trapping errors, it's going to have to cooperate.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Markus Schiltknecht
Date:
Subject: Re: Integrating Replication into Core
Next
From: Tom Lane
Date:
Subject: Re: bad plan with custom data types