Re: Deleting a table file does not raise an error when the table is touched afterwards, why?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Westermann <daniel(dot)westermann(at)dbi-services(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Deleting a table file does not raise an error when the table is touched afterwards, why?
Date: 2016-05-30 20:45:27
Message-ID: CAKFQuwYg+NCe-+UXatq1pJLnGLd++sqD0kyt30kELzsj1t9j+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, May 30, 2016 at 3:32 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> ​I have to think that we can reasonably ascribe unexpected system state to
> causes other than human behavior. In both of the other examples PostgreSQL
> would fail to start so I'd say we have expected behavior in the face of
> those particular unexpected system states.
>

Alex Ignatov started a new thread was started on this topic as well...​

https://www.postgresql.org/message-id/c571dfc5-91b0-0df2-4e3f-45bc94c11759@postgrespro.ru

I posted a link to this thread on his new one as well.

David J.​

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex Ignatov 2016-05-30 21:12:26 Re: Silent data loss in its pure form
Previous Message David G. Johnston 2016-05-30 20:42:09 Re: Silent data loss in its pure form