Re: Continue work on changes to recovery.conf API

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Continue work on changes to recovery.conf API
Дата
Msg-id 26178006-74c0-4599-0125-6bf9eb489e96@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: Continue work on changes to recovery.conf API  (David Steele <david@pgmasters.net>)
Ответы Re: Continue work on changes to recovery.conf API  (Stephen Frost <sfrost@snowman.net>)
Re: Continue work on changes to recovery.conf API  (Andres Freund <andres@anarazel.de>)
Re: Re: Continue work on changes to recovery.conf API  (David Steele <david@pgmasters.net>)
Список 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 по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: SSL tests failing with "ee key too small" error on Debian SID
Следующее
От: Tom Lane
Дата:
Сообщение: Re: SSL tests failing with "ee key too small" error on Debian SID