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 ec74a8ae-8d25-6d60-1db4-907c7999acbb@2ndquadrant.com
Whole thread Raw
In response to Re: Continue work on changes to recovery.conf API  (Andres Freund <andres@anarazel.de>)
Responses Re: Continue work on changes to recovery.conf API
List pgsql-hackers
On 25/11/2018 21:39, Andres Freund wrote:
> On 2018-11-25 13:24:15 -0500, Stephen Frost wrote:
>> - User performs a backup with pg_basebackup -R
>> - Replica is then promoted to be a primary
>> - User performs a backup with pg_basebackup -R on the new primary
>> - Duplicate entries end up in postgresql.auto.conf.  Ew.
> Why don't we put recovery entries into postgresql.recovery.conf or such?
> And overwrite rather than append?

Adding more such sub-configuration files would be easy to do and has
some merit, but the devil is in the details.  In what order would those
files be read?  Who is supposed to write to it, is it reserved for
pg_basebackup use only?  If you choose to use this particular name, is
it not used when not in recovery?  Does this file belong in the data
directory or the configuration directory?  Which choice will offend
packagers the least?  Etc.

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


pgsql-hackers by date:

Previous
From: "Ideriha, Takeshi"
Date:
Subject: RE: Protect syscache from bloating with negative cache entries
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: shared-memory based stats collector