| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: block-level incremental backup |
| Date: | 2019-04-09 17:56:23 |
| Message-ID: | CA+TgmoZb2b_ZARUNABSa3JyGKCwANGfGJ-Dhiw98dKeb1-fPyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 9, 2019 at 12:32 PM Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru> wrote:
> In pg_probackup we have remote restore via SSH in the beta state. But
> SSH isn't an option for in-core approach I think.
That's a little off-topic for this thread, but I think we should have
some kind of extensible mechanism for pg_basebackup and maybe other
tools, so that you can teach it to send backups to AWS or your
teletype or etch them on stone tablets or whatever without having to
modify core code. But let's not design that mechanism on this thread,
'cuz that will distract from what I want to talk about here. Feel
free to start a new thread for it, though, and I'll jump in. :-)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-04-09 18:29:09 | Re: Zedstore - compressed in-core columnar storage |
| Previous Message | Robert Haas | 2019-04-09 17:54:00 | Re: block-level incremental backup |