Re: Server Crash - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: Server Crash
Date
Msg-id dcc563d10804220921n688d16f6h4b5f921b5b38b48b@mail.gmail.com
Whole thread Raw
In response to Re: Server Crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Server Crash  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Tue, Apr 22, 2008 at 10:06 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > From: Scott Marlowe [mailto:scott.marlowe@gmail.com]
>
> >> Kill -9 is the "shoot it in the head" signal.  It is not
>  >> generated by postgresql in normal operation.  It can be
>  >> generated by "pg_ctl -m immediate stop" .  At least I think
>  >> that's what signal it sends.
>
>  Just for the archives: Postgres never generates kill -9 at all.
>  (Immediate stop uses SIGQUIT, instead.)  When you see that in
>  the log, you can be sure it was a manual action or the OOM killer.

Thanks.  Just wondering, what's the difference in behavior from
pgsql's perspective from sigquit and siqkill?  Is sigkill more
dangerous than sigquit?

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Server Crash
Next
From: Tom Lane
Date:
Subject: Re: Server Crash