| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extending BASE_BACKUP in replication protocol: incremental backup and backup format |
| Date: | 2014-01-14 13:41:37 |
| Message-ID: | 20140114134137.GD8537@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-01-14 14:40:46 +0100, Magnus Hagander wrote:
> On Tue, Jan 14, 2014 at 2:18 PM, Andres Freund <andres(at)2ndquadrant(dot)com>wrote:
>
> > On 2014-01-14 14:12:46 +0100, Magnus Hagander wrote:
> > > Either way - if we can do this in a safe way, it sounds like a good idea.
> > > It would be sort of like rsync, except relying on the fact that we can
> > look
> > > at the LSN and don't have to compare the actual files, right?
> >
> > Which is an advantage, yes. On the other hand, it doesn't fix problems
> > with a subtly broken replica, e.g. after a bug in replay, or disk
> > corruption.
> >
> >
> Right. But neither does rsync, right?
Hm? Rsync's really only safe with --checksum and with that it definitely
should fix those?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2014-01-14 13:41:48 | Re: Extending BASE_BACKUP in replication protocol: incremental backup and backup format |
| Previous Message | Magnus Hagander | 2014-01-14 13:40:46 | Re: Extending BASE_BACKUP in replication protocol: incremental backup and backup format |