RE: automatic restore point - Mailing list pgsql-hackers

From Yotsunaga, Naoki
Subject RE: automatic restore point
Date
Msg-id 8E9126CB6CE2CD42962059AB0FBF7B0DBF8BC0@g01jpexmbkw23
Whole thread Raw
In response to Re: automatic restore point  (Michael Paquier <michael@paquier.xyz>)
Responses Re: automatic restore point  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
>-----Original Message-----
>From: Michael Paquier [mailto:michael@paquier.xyz] 
>Sent: Wednesday, July 11, 2018 3:34 PM

>Well, if you put in place correct measures from the start you would not have problems.  
>It seems to me that there is no point in implementing something which is a solution for a very narrow case, where the
userhas shot his own foot to begin with. 
 
>Having backups anyway is mandatory by the way, standby replicas are not backups.

I think that the Undo function of AWS and Oracle's Flashback function are to save such users, and it is a function to
preventhuman error.
 
So, how about postgres implementing such a function?
 
Also, as an approach to achieving the goal, I thought about outputting lsn to the server log when a specific command
wasexecuted.
 
 
I do not think the source code of postgres will be complicated when implementing this function.
Do you feel it is too complicated?

-------
Naoki Yotsunaga

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Constraint documentation
Next
From: Pierre Ducroquet
Date:
Subject: [PATCH] LLVM tuple deforming improvements