From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Make pg_basebackup -x stream the default |
Date: | 2016-12-15 19:36:36 |
Message-ID: | f9fd5558-e62a-2d51-ab9c-28c7b341b875@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/15/16 1:27 PM, Magnus Hagander wrote:
> On Thu, Dec 15, 2016 at 7:23 PM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com
> <mailto:peter(dot)eisentraut(at)2ndquadrant(dot)com>> wrote:
>
> On 11/8/16 12:45 PM, Magnus Hagander wrote:
> > Per some discussions with a number of different people at pgconfeu, here
> > is a patch that changes the default mode of pg_basebackup to be
> > streaming the wal, as this is what most users would want -- and those
> > that don't want it have to make other changes as well. Doing the "most
> > safe" thing by default is a good idea.
> >
> > The new option "-x none" is provided to turn this off and get the
> > previous behavior back.
>
> I would have expected that the "stream" method would become the default.
> Just a short while ago it was proposed to remove the "fetch" method
> altogether, and it was only kept because of some niche use cases. I
> don't think "fetch" is the most safe method, because it requires
> wal_keep_segments to be configured.
>
>
> Eh. Yes. That's exactly what this patch does, is it not?
Yes, I misread the patch. Works for me, then.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2016-12-15 20:20:59 | Re: Proposal for changes to recovery.conf API |
Previous Message | Magnus Hagander | 2016-12-15 18:38:50 | Re: Make pg_basebackup -x stream the default |