Re: why not kill -9 postmaster

Поиск
Список
Период
Сортировка
От Ian Harding
Тема Re: why not kill -9 postmaster
Дата
Msg-id 725602300610200745s13ad1f1dy3e53c5a127fb666e@mail.gmail.com
обсуждение исходный текст
Ответ на Re: why not kill -9 postmaster  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: why not kill -9 postmaster  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
On 10/20/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Shane Ambler wrote:
> >> The one thing worse than kill -9 the postmaster is pulling the power
> >> cord out of the server. Which is what makes UPS's so good.
> >>
> >> If your server is changing the data file on disk and you pull the power
> >> cord, what chance do you expect of reading that data file again?
>
> > 1.  That's what we have WAL for.  The only thing that can really kill
> > you is the use of non-battery-backed write cache.
>
> The important distinction here is "will you lose data" vs "can you start
> a new server without tedious manual intervention" (ipcrm etc).  kill -9
> won't lose data, but you may have to clean up after it.  And, as Andreas
> already noted, some people have been seen to mess up the manual
> intervention part badly enough to cause data loss by themselves.
> Personally I think the TIP that's really needed is "never remove
> postmaster.pid by hand".
>

When the machine crashes, don't you have to remove the pid file by
hand to get the Postgres to start?  I seem to remember having to do
that....

- Ian Never-Say-Never Harding

В списке pgsql-general по дате отправления:

Предыдущее
От: "Peter Bauer"
Дата:
Сообщение: Re: Overload after some minutes, please help!
Следующее
От: Jeff Davis
Дата:
Сообщение: strange encoding behavior