Re: could recovery_target_timeline=latest be the default in standbymode? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: could recovery_target_timeline=latest be the default in standbymode?
Date
Msg-id 20181227231514.GD2196@paquier.xyz
Whole thread Raw
In response to Re: could recovery_target_timeline=latest be the default in standbymode?  (David Steele <david@pgmasters.net>)
Responses Re: could recovery_target_timeline=latest be the default in standbymode?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Thu, Dec 27, 2018 at 06:36:23PM +0200, David Steele wrote:
> I like the idea of defaulting to the latest timeline since this is what you
> want to do most of the time, but I think we'd then need a value for
> following the current timelime, i.e. the one that the backup was taken on
> (which is the current default).
>
> [...]
>
> I would recommend:
>
> 1) Make the default for recovery_target_timeline always be latest.
> 2) Add a new value, current, that replicates the current behavior.

Yes, I was also thinking something among those lines, and the patch is
a bit confusing by linking standby mode with latest timeline.  It
seems to me that switching the default value to "latest" at GUC level
would be the way to go, instead of picking up the TLI from the control
file.  Introducing a new value which maps to the current empty value
may be useful as well, like "control_file"?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: row filtering for logical replication
Next
From: Michael Paquier
Date:
Subject: Re: Offline enabling/disabling of data checksums