From: Michael Paquier <michael@paquier.xyz>
To: Yotsunaga, Naoki <yotsunaga.naoki@jp.fujitsu.com>
Cc: Postgres hackers <pgsql-hackers@postgresql.org>
Subject: Re: automatic restore point
Date: Tue, 3 Jul 2018 10:16:50 +0900
Message-ID: <20180703011650.GD2159@paquier.xyz> (raw)
In-Reply-To: <8E9126CB6CE2CD42962059AB0FBF7B0DBF3ADD@g01jpexmbkw23>
References: <8E9126CB6CE2CD42962059AB0FBF7B0DBE3167@g01jpexmbkw23>
<20180626053035.GD31353@paquier.xyz>
<8E9126CB6CE2CD42962059AB0FBF7B0DBF3ADD@g01jpexmbkw23>
On Tue, Jul 03, 2018 at 01:07:41AM +0000, Yotsunaga, Naoki wrote:
>> There is also recovery_target_lsn which is new as of v10.
> In this method, it is necessary to look at a lsn position before operating.
> But I assume the user who did not look it before operating.
> So I think that this method is not appropriate.
You should avoid top-posting on the mailing lists, this breaks the
consistency of the thread.
>> So basically what you are looking for here is a way to enforce a
>> restore point to be created depending on a set of pre-defined
>> conditions? How would you define and choose those?
>
> I understand that I was asked how to set up a command to apply this function.
> Ex) DROP = on
> TRUNCATE = off
> Is my interpretation right?
> If my interpretation is correct, all the above commands will be
> applied.
> When this function is turned on, this function works when all the
> above commands are executed.
Yeah, but based on which factors are you able to define that such
conditions are enough to say that this feature is fully-compliant with
user's need, and how can you be sure that this is not going to result in
an additional maintenance burden if you need to define a new set of
conditions in the future. For example an operator has issued a costly
ALTER TABLE which causes a full table rewrite, which could be also an
operation that you would like to prevent. Having a set of GUCs which
define such low-level behavior is not really user-friendly.
--
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
Subject: Re: automatic restore point
In-Reply-To: <20180703011650.GD2159@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