| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Including replication slot data in base backups |
| Date: | 2014-04-04 12:44:57 |
| Message-ID: | 20140404124457.GA14419@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-04-04 21:42:33 +0900, Michael Paquier wrote:
> On Wed, Apr 2, 2014 at 10:27 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > The new master won't necessarily have all the neccessary WAL available, no?
> No, they won't have it, and things begin to get bad once a base backup
> includes a slot that has a non-null value of restart_lsn.
In other words, every slot that has been used.
> I imagine
> that if we want to guarantee the correctness of a replication slot we
> would need to fetch from archives the necessary WAL files needed for
> it when a node is in recovery, which is not something that this patch
> does...
Does that mean you "retract" the patch?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-04-04 12:57:26 | Re: Including replication slot data in base backups |
| Previous Message | Michael Paquier | 2014-04-04 12:42:33 | Re: Including replication slot data in base backups |