Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Postmaster can't stop with pg_ctl
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- Cc: takuya koide <koide-txa(at)necst(dot)nec(dot)co(dot)jp>, pgsql-bugs(at)postgresql(dot)org
- Subject: Re: Postmaster can't stop with pg_ctl
- Date: Wed, 25 Apr 2007 10:22:25 -0400
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes: > takuya koide wrote: >> 4) send 'SIGSTOP' signal to postgres > If you "stop" a process by SIGSTOP you must make it run again with > SIGCONT. Otherwise it's just not processing signals, so it'll obviously > not shut down. I don't think this is a bug. SIGSTOP is a debugging tool, which would be rendered nigh useless if the postmaster tried to override it automatically. So definitely NOTABUG in my opinion too. regards, tom lane
- Follow-Ups:
- Re: Postmaster can't stop with pg_ctl
- From: takuya koide
- Re: Postmaster can't stop with pg_ctl
- References:
- Postmaster can't stop with pg_ctl
- From: takuya koide
- Re: Postmaster can't stop with pg_ctl
- From: Alvaro Herrera
- Postmaster can't stop with pg_ctl
- Prev by Date: Re: Postmaster can't stop with pg_ctl
- Next by Date: pg_dump doesn't properly honor -O for sequences
- Previous by thread: Re: Postmaster can't stop with pg_ctl
- Next by thread: Re: Postmaster can't stop with pg_ctl
- Indexes: