Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUCpseudo-variable. - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUCpseudo-variable.
Date
Msg-id f4b63881-6bc3-5040-5c43-ecb333f76316@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.  (Elvis Pranskevichus <elprans@gmail.com>)
Responses Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.  (Elvis Pranskevichus <elprans@gmail.com>)
List pgsql-hackers
Tree view 
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)?

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

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] increasing the default WAL segment size
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Aggregates and row types