Re: inconsistent state after crash recovery

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: inconsistent state after crash recovery
Дата
Msg-id 13112.1374841625@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: inconsistent state after crash recovery  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: inconsistent state after crash recovery  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
Re: inconsistent state after crash recovery  (Robert Haas <robertmhaas@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Design proposal: fsync absorb linear slider