| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | "Stephen Harris" <lists(at)spuddy(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Shutting down a warm standby database in 8.2beta3 |
| Date: | 2006-11-20 16:30:04 |
| Message-ID: | 7306.1164040204@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> I haven't really been folliowing this thread. What exactly is it you
> want to accomplish (maybe there is a different way to fix it on win32)?
> Kill a process along with all it's subprocesses?
Right. The problem (as seen on Unix) is that if the recovery subprocess
is waiting for a recovery_command script to complete, it doesn't react
to SIGQUIT (because system() ignores SIGQUIT) and the script doesn't
react either (because it never gets the signal at all). We'd like
"pg_ctl stop -m immediate" to abort the script and then have the
recovery process fail, allowing restart later. More generally, it
seems like any time a backend is executing system(), the called script
ought to be subject to SIGINT or SIGQUIT signals sent to the backend
by the postmaster.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2006-11-20 16:30:11 | Re: Eliminating bad characters from a database for upgrading from 7.4 to 8.1 |
| Previous Message | Magnus Hagander | 2006-11-20 16:23:09 | Re: [GENERAL] Shutting down a warm standby database in 8.2beta3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-20 16:32:22 | Re: Transaction start in pg_stat_activity |
| Previous Message | Simon Riggs | 2006-11-20 16:25:11 | Re: Transaction start in pg_stat_activity |