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

From: Elvis Pranskevichus <elprans(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.
Date: 2017-03-22 12:25:20
Message-ID: 7888047.S8F2uOXGmr@hammer.magicstack.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2017-03-22 12:30:40 Re: Patch: Write Amplification Reduction Method (WARM)
Previous Message Petr Jelinek 2017-03-22 12:12:53 Re: logical replication access control patches