From: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
---|---|
To: | Ralf Schuchardt <rasc(at)gmx(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: What happens when you kill the postmaster? |
Date: | 2010-01-13 11:27:00 |
Message-ID: | 92869e661001130327k4808fd21kce95ecac1851c129@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2010/1/13 Ralf Schuchardt <rasc(at)gmx(dot)de>
> Hi,
>
> on one of our Mac servers an update (Remote Desktop Client) killed
> yesterday the postmaster process. Apparently this did not have any influence
> on existing connections and therefore was not detected until some time
> later, when no connection for a backup could be made.
>
> I have then closed all apps with connections to the database. This brought
> the whole cluster down. It restarted then with some transaction log rollback
> messages and seems to be running fine since then.
>
> Can I now expect that the database is in a consistent state, or must I
> assume the database is corrupted?
> I could run a dump-all without problems and there are rows created after
> the death the postmaster.
>
>
It depends on the signal which was sent to the postgres process.
AFAIK, only SIGKILL (unconditional kill) can make some damage to the
database.
see http://www.postgresql.org/docs/8.4/static/app-postgres.html forfull
explanation
> Thanks.
>
> Ralf Schuchardt
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
Filip Rembiałkowski
JID,mailto:filip(dot)rembialkowski(at)gmail(dot)com
http://filip.rembialkowski.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Eichenberger | 2010-01-13 13:03:54 | autovacuum_naptime seems to take minutes for seconds |
Previous Message | Craig Ringer | 2010-01-13 11:05:58 | Re: Collate order on Mac OS X, text with diacritics in UTF-8 |