| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: block-level incremental backup |
| Date: | 2019-04-09 21:07:39 |
| Message-ID: | 1f3273f7-97e3-1e52-8510-9a7b43b21e56@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-04-09 17:48, Robert Haas wrote:
> It will
> probably be more efficient in many cases to instead scan all the WAL
> generated since that LSN and extract block references from it, but
> that is only possible if the server has all of that WAL available or
> can somehow get it from the archive.
This could be a variant of a replication slot that preserves WAL between
incremental backup runs.
> 3. There should be a new tool that knows how to merge a full backup
> with any number of incremental backups and produce a complete data
> directory with no remaining partial files.
Are there by any chance standard file formats and tools that describe a
binary difference between directories? That would be really useful here.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2019-04-09 21:08:11 | Re: Zedstore - compressed in-core columnar storage |
| Previous Message | Ashwin Agrawal | 2019-04-09 21:03:09 | Re: Zedstore - compressed in-core columnar storage |