| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Yang Jie' <yangjie(at)highgo(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Implementation of Flashback Query |
| Date: | 2018-10-18 00:06:47 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1FAE40CB@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Yang Jie [mailto:yangjie(at)highgo(dot)com]
> Delayed cleanup, resulting in performance degradation, what are the
> solutions recommended?
> What do you suggest for the flashback feature?
> Although postgres has excellent backup and restore capabilities, have you
> considered adding flashbacks?
Great proposal, I appreciate it.
Regarding the bloat, check the recent mail threads titled "undo xxx". A new table storage format is being developed to use undo logs like Oracle and MySQL instead of generating dead tuples.
How about the possibility of adding a feature like Flashback Drop to restore dropped and truncated tables? I sometimes saw customers who mistakenly dropped or truncated tables but didn't have any backup.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-10-18 00:10:28 | Re: DSM robustness failure (was Re: Peripatus/failures) |
| Previous Message | Ants Aasma | 2018-10-17 23:14:00 | Checkpoint start logging is done inside critical section |