Re: block-level incremental backup
Artur Zakirov <a.zakirov@postgrespro.ru>
From: Arthur Zakirov <a.zakirov@postgrespro.ru>
To: Robert Haas <robertmhaas@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-04-09T16:32:30Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Don't call data type input functions in GUC check hooks
- 21f428ebde39 12.0 cited
Hello, On 09.04.2019 18:48, Robert Haas wrote: > - It would also be nice if pg_basebackup could write backups to places > other than the local disk, like an object store, a tape drive, etc. > But that also sounds like a separate effort. > > Thoughts? (Just thinking out loud) Also it might be useful to have remote restore facility (i.e. if pg_combinebackup could write to non-local storage), so you don't need to restore the instance into a locale place and copy/move to the remote machine. But it seems to me that it is the most nontrivial feature and requires much more effort than other points. 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. -- Arthur Zakirov Postgres Professional: http://www.postgrespro.com Russian Postgres Company