From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Daniel Westermann <daniel(dot)westermann(at)dbi-services(dot)com> |
Cc: | Postgres General Postgres General <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 16:15:11 |
Message-ID: | CANP8+jLNL4xdQstx8yQc1iOZ63eA06E-_sihMrhm8gNX=F5HxQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 30 May 2016 at 16:35, Daniel Westermann <
daniel(dot)westermann(at)dbi-services(dot)com> wrote:
...
> Then I delete the file:
>
...
> No issue in the log. This is probably coming from the cache, isn't it? Is
> this intended and safe?
>
Postgres manages your data for you. What you're doing is not a supported
use case and I recommend not to do that in the future.
> Can someone please tell me the intention behind that? From my point of
> view this is dangerous. If nobody is monitoring the log (which sadly is the
> case in reality) nobody will notice that only parts of the table are there.
> Wouldn't it be much more safe to raise an error as soon as the table is
> touched?
>
How would we know that an external agent had deleted the file? What action
should we take if we did notice?
It's a very good thing that we remain flying even with multiple bullet
holes in the wings.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2016-05-30 16:24:10 | Re: pglogical |
Previous Message | Francisco Olarte | 2016-05-30 16:13:49 | Re: Deleting a table file does not raise an error when the table is touched afterwards, why? |