| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: where should I stick that backup? |
| Date: | 2020-04-20 06:36:03 |
| Message-ID: | CAA4eK1LDfwfbUU++wwbYO=_uVZQQRLsmorUdpHhF7MR4N1t_CA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 13, 2020 at 5:57 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
> There's a couple of other pieces here that I think bear mentioning. The
> first is that pgBackRest has an actual 'restore' command- and that works
> with the filters and works with the storage drivers, so what you're
> looking at when it comes to these interfaces isn't just "put a file" but
> it's also "get a file". That's actually quite important to have when
> you start thinking about these more complicated methods of doing
> backups.
>
I also think it is important to provide a way or interface to restore
the data user has backed up using whatever new API we provide as here.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-04-20 06:58:34 | Re: fixing old_snapshot_threshold's time->xid mapping |
| Previous Message | Dilip Kumar | 2020-04-20 06:34:44 | Re: fixing old_snapshot_threshold's time->xid mapping |