Re: could recovery_target_timeline=latest be the default in standby mode?

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Sergei Kornilov <sk(at)zsrv(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: could recovery_target_timeline=latest be the default in standby mode?
Date: 2018-12-27 11:02:34
Message-ID: 249bd41d-0385-3038-4394-a42f00e1a045@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22/12/2018 00:38, Michael Paquier wrote:
> On Fri, Dec 21, 2018 at 01:54:20PM +0300, Sergei Kornilov wrote:
>> I am +1 for recovery_target_timeline=latest by default. This is
>> common case in my opinion.
>
> I agree also that switching to the latest timeline should be the
> default. People get confused because of the current default.

How about this patch then?

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
0001-Always-use-latest-timeline-in-standby-mode.patch text/plain 7.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2018-12-27 11:14:03 Re: [PATCH] pg_hba.conf : new auth option : clientcert=verify-full
Previous Message Pavel Stehule 2018-12-27 11:01:34 Re: PostgreSQL partition tables use more private memory