| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Satoshi Nagayasu <snaga(at)uptime(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: inconsistent state after crash recovery |
| Date: | 2013-08-02 12:19:10 |
| Message-ID: | CA+TgmobN0+f4efOFS9KybDOr8pr6ed47ig4fdycwwtG3H3pOZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 2, 2013 at 8:17 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Fri, Jul 26, 2013 at 8:27 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> would you expect crash recovery to notice the disappearance of a file
>>> that was touched nowhere in the replayed actions?
>
>> Eh, maybe not. But should we try harder to detect the unexpected
>> disappearance of one that is?
>
> We do, don't we? The replay stuff should complain unless it sees a drop
> or truncate covering any unaccounted-for pages.
Hmm. Yeah. But the OP seems to think it doesn't work.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-08-02 12:21:37 | Re: Immediate shutdown causes the assertion failure in 9.4dev |
| Previous Message | Tom Lane | 2013-08-02 12:17:47 | Re: inconsistent state after crash recovery |