Re: Make pg_basebackup -x stream the default

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Make pg_basebackup -x stream the default
Date: 2016-12-15 18:36:53
Message-ID: 42b16b14-1538-d76b-a4a6-81723f2c3369@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/15/2016 10:23 AM, Peter Eisentraut 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.

IMO, if you are using fetch just using archive_command. Let's rip it out
of pg_basebackup or at least deprecate it.

jD

>

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2016-12-15 18:38:50 Re: Make pg_basebackup -x stream the default
Previous Message Magnus Hagander 2016-12-15 18:27:38 Re: Make pg_basebackup -x stream the default