Re: Continue work on changes to recovery.conf API - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Continue work on changes to recovery.conf API
Date
Msg-id 26178006-74c0-4599-0125-6bf9eb489e96@2ndquadrant.com
Whole thread Raw
In response to Re: Continue work on changes to recovery.conf API  (David Steele <david@pgmasters.net>)
Responses Re: Continue work on changes to recovery.conf API
Re: Continue work on changes to recovery.conf API
Re: Re: Continue work on changes to recovery.conf API
List pgsql-hackers
On 27/11/2018 13:21, David Steele wrote:
> I would prefer a specific file that will be auto-included into
> postgresql.conf when present but be ignored when not present.  Some
> settings are generally ephemeral (recovery_target_time) and it would be
> nice for them to go away.  When recovery is complete the file would be
> renamed to .done just as recovery.conf is now.

That might be a useful facility, but it wouldn't really address the
pg_basebackup -R issue, because that creates settings that you don't
want going away in this manner.  You'd then need two separate such
files, one for targeted recovery that goes away when recovery ends, and
one that is automatically included that pg_basebackup can overwrite at will.

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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: SSL tests failing with "ee key too small" error on Debian SID
Next
From: Tom Lane
Date:
Subject: Re: SSL tests failing with "ee key too small" error on Debian SID