Re: [HACKERS] Proposal for changes to recovery.conf API

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] Proposal for changes to recovery.conf API
Дата
Msg-id 083cbe78-2ba6-956c-0ab5-9228987674dc@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Proposal for changes to recovery.conf API  (Simon Riggs <simon@2ndquadrant.com>)
Ответы Re: [HACKERS] Proposal for changes to recovery.conf API  (Fujii Masao <masao.fujii@gmail.com>)
Re: [HACKERS] Proposal for changes to recovery.conf API  (Simon Riggs <simon@2ndquadrant.com>)
Список pgsql-hackers
On 1/1/17 4:14 PM, Simon Riggs wrote:
> OK, so here's the patch, plus doc cleanup patch.

I don't think this patch is likely to succeed if we throw in more ideas
in every round.

I think we have or are approaching agreement on moving recovery.conf
into postgresql.conf, making the settings reloadable, and adding signal
(formerly trigger) files to trigger recovery or standby.  I think that
is a useful change, but it's already big enough and needs extensive
reviewing and testing.

All the other stuff, such as regrouping the recovery parameters,
removing the hot_standby setting, renaming the primary_* parameters,
making the directory of the signal files configurable, should be
separate patches that should be discussed separately.  I think the
arguments for these latter changes are weaker, and tactically I would
focus on getting the recovery.conf move in before thinking about all the
other ones.

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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: [HACKERS] increasing the default WAL segment size
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE