From: Michael Paquier <michael@paquier.xyz>
To: Yotsunaga, Naoki <yotsunaga.naoki@jp.fujitsu.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Postgres hackers <pgsql-hackers@postgresql.org>
Subject: Re: automatic restore point
Date: Tue, 3 Jul 2018 10:21:59 +0900
Message-ID: <20180703012159.GE2159@paquier.xyz> (raw)
In-Reply-To: <8E9126CB6CE2CD42962059AB0FBF7B0DBF3ACC@g01jpexmbkw23>
References: <8E9126CB6CE2CD42962059AB0FBF7B0DBE3167@g01jpexmbkw23>
<CAKFQuwamx96qu6GAM8OuoM3DNEockiiiE=VOx1LV0_Hag5bOrQ@mail.gmail.com>
<CAMsGm5cbv6BwqzsUHGVDUvn5yMePhyZBCfPhND88QAWv6MqwOA@mail.gmail.com>
<20180626051600.GC31353@paquier.xyz>
<8E9126CB6CE2CD42962059AB0FBF7B0DBF3ACC@g01jpexmbkw23>
On Tue, Jul 03, 2018 at 01:06:31AM +0000, Yotsunaga, Naoki wrote:
>> I'd rather spend effort making the initial execution of said commands
>> less likely.
>
> I think that the function to prohibit DELETE and UPDATE without a
> WHERE clause in the later response is good way.
This has popped up already in the lists in the past.
> But I think that it is impossible to completely eliminate the failure
> of the other commands. For example, drop the wrong table.
This kind of thing is heavily application-dependent. For example, you
would likely not care if an operator, who has newly-joined the team in
charge of the maintenance of this data, drops unfortunately a table
which includes logs from 10 years back, and you would very likely care
about a table dropped which has user's login data. My point is that you
need to carefully design the shape of the configuration you would use,
so as any application's admin would be able to cope with it, for example
allowing exclusion filters with regular expressions could be a good idea
to dig into. And also you need to think about it so as it is backward
compatible.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: michael@paquier.xyz, yotsunaga.naoki@jp.fujitsu.com, david.g.johnston@gmail.com
Subject: Re: automatic restore point
In-Reply-To: <20180703012159.GE2159@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox