From: | takuya koide <koide-txa(at)necst(dot)nec(dot)co(dot)jp> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Postmaster can't stop with pg_ctl |
Date: | 2007-04-26 06:12:13 |
Message-ID: | 20070426145145.CE31.KOIDE-TXA@necst.nec.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thank you for your reply.
On Wed, 25 Apr 2007 10:22:25 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
For end-user, Debugging is not important and daily working, too.
So for developper, if PostgreSQL have a debug option, it seems that it is no problem.
(When it is used debug option, it not shutdown as like current working)
Thank you.
Best Regards
---
Takuya Koide
NEC System Technologies, Ltd.
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Santini | 2007-04-26 07:54:19 | BUG #3254: unexpected data beyond EOF in block |
Previous Message | takuya koide | 2007-04-26 05:50:49 | Re: Postmaster can't stop with pg_ctl |