| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Stephen Harris" <lists(at)spuddy(dot)org> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Shutting down a warm standby database in 8.2beta3 |
| Date: | 2006-11-20 16:23:09 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA3594D@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> This would fix the problem on Unixen with setsid, which
> should be pretty much all of them; on any that don't have it,
> the behavior doesn't change. Still leaves Windows out in the
> cold, but I don't see that we have anything much we can do
> about it there --- Windows users will just have to know to
> kill the child script process instead of the postmaster.
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?
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-20 16:30:04 | Re: [GENERAL] Shutting down a warm standby database in 8.2beta3 |
| Previous Message | Tom Lane | 2006-11-20 16:20:41 | Re: [GENERAL] Shutting down a warm standby database in 8.2beta3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-11-20 16:25:11 | Re: Transaction start in pg_stat_activity |
| Previous Message | Tom Lane | 2006-11-20 16:20:41 | Re: [GENERAL] Shutting down a warm standby database in 8.2beta3 |