Re: inconsistent state after crash recovery - Mailing list pgsql-hackers

From Tom Lane
Subject Re: inconsistent state after crash recovery
Date
Msg-id 13112.1374841625@sss.pgh.pa.us
Whole thread Raw
In response to Re: inconsistent state after crash recovery  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: inconsistent state after crash recovery
Re: inconsistent state after crash recovery
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2013-07-26 13:33:13 +0900, Satoshi Nagayasu wrote:
>> Is this expected or acceptable?

> I'd say it's both.

Postgres is built on the assumption that the underlying filesystem is
reliable, ie, once you've successfully fsync'd some data that data won't
disappear.  If the filesystem fails to honor that contract, it's a
filesystem bug not a Postgres bug.  Nor is it reasonable to expect
Postgres to be able to detect every such violation.  As an example,
would you expect crash recovery to notice the disappearance of a file
that was touched nowhere in the replayed actions?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Next
From: Tom Lane
Date:
Subject: Re: Design proposal: fsync absorb linear slider