Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.

Поиск
Список
Период
Сортировка
От Elvis Pranskevichus
Тема Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.
Дата
Msg-id 7888047.S8F2uOXGmr@hammer.magicstack.net
обсуждение исходный текст
Ответ на Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUCpseudo-variable.  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.
Список pgsql-hackers
On Tuesday, March 21, 2017 11:50:38 PM EDT Peter Eisentraut wrote:
> On 3/17/17 13:56, Elvis Pranskevichus wrote:
> > Currently, clients wishing to know when the server exits hot standby
> > have to resort to polling, which is often suboptimal.
> > 
> > This adds the new "in_hot_standby" GUC variable that is reported via
> > a ParameterStatus message.
> 
> The terminology chosen here is not very clear.  What is the opposite
> of "in hot standby"?  Warm standby?  Cold standby?  Not standby at
> all? Promoted to primary (writable)?

The opposite means primary.  I can flip the GUC name to "is_primary", if 
that's clearer.
                              Elvis



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

Предыдущее
От: Petr Jelinek
Дата:
Сообщение: Re: [HACKERS] logical replication access control patches
Следующее
От: Greg Stark
Дата:
Сообщение: Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)