| From: | "Yotsunaga, Naoki" <yotsunaga(dot)naoki(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Michael Paquier' <michael(at)paquier(dot)xyz> |
| Cc: | Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: automatic restore point |
| Date: | 2018-07-13 08:16:00 |
| Message-ID: | 8E9126CB6CE2CD42962059AB0FBF7B0DBF8BC0@g01jpexmbkw23 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>-----Original Message-----
>From: Michael Paquier [mailto:michael(at)paquier(dot)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 user has 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 prevent human 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 was executed.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre Ducroquet | 2018-07-13 08:20:42 | [PATCH] LLVM tuple deforming improvements |
| Previous Message | Peter Eisentraut | 2018-07-13 08:14:10 | Re: Constraint documentation |