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: 2007-04-25 14:22:25
Message-ID: 21884.1177510945@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Davis 2007-04-25 18:36:32 pg_dump doesn't properly honor -O for sequences
Previous Message Alvaro Herrera 2007-04-25 13:44:47 Re: Postmaster can't stop with pg_ctl