From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: How to shoot yourself in the foot: kill -9 postmaster |
Date: | 2001-03-06 18:20:40 |
Message-ID: | Pine.LNX.4.30.0103061918110.778-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Lamar Owen writes:
> > case when the postmaster does not come down after 60 seconds. But this is
> > really no problem for the issue at hand because if you do a normal
> > runlevel switch then the postmaster will simply keep running, and during a
> > system shutdown all the backends are going to die anyway.
>
> Only if each and every shutdown script succeeds in its task. And I have
> to make sure that the RPM's shipping script successfully pulls down the
> system in an orderly fashion -- of course, I don't have to worry about
> the case where a postmaster is going to be started back up if we are in
> system shutdown -- but, as Tom also stated, I can't assume I'm in the
> system's death throes when called with the stop parameter.
Well, if you have something clever you want to do if the postmaster
doesn't come down after an orderly shutdown then please share it. The
current alternatives are 'leave running' or 'kill -9'. I know I'd prefer
the former.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
From | Date | Subject | |
---|---|---|---|
Next Message | Alfred Perlstein | 2001-03-06 18:22:46 | Re: How to shoot yourself in the foot: kill -9 postmaster |
Previous Message | Tom Lane | 2001-03-06 18:18:53 | Re: AW: AW: AW: AW: WAL-based allocation of XIDs is insecur e |