Re: could not read block 77 of relation 1663/16385/388818775 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: could not read block 77 of relation 1663/16385/388818775
Date
Msg-id 7377.1227212809@sss.pgh.pa.us
Whole thread Raw
In response to Re: could not read block 77 of relation 1663/16385/388818775  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-bugs
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Craig Ringer wrote:
>> Is there any chance you have EVER hard-killed the postmaster manually
>> (eg with "kill -9" or "kill -KILL")?

> There is safeguards against that. If postmaster dies, the backends
> should die quickly and gracefully too. And postmaster refuses to restart
>   until all the backends have died and detached from the shared memory
> segment.

A sufficiently bull-headed DBA can defeat those safeguards though ---
from memory, manually removing postmaster.pid and then starting a new
postmaster while old backends remain alive is the ticket to data
corruption.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: could not read block 77 of relation 1663/16385/388818775
Next
From: Sushil
Date:
Subject: Re: executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error