| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Elvis Pranskevichus <elprans(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, 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 18:09:13 |
| Message-ID: | CA+TgmoZFqkqL7t1LWs-2jJTrPXQXVRPGTquUJaUD4BeSAPgdZA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 22, 2017 at 8:25 AM, Elvis Pranskevichus <elprans(at)gmail(dot)com> wrote:
> 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.
Hmm, I don't find that clearer. "hot standby" has a very specific
meaning; "primary" isn't vague, but I would say it's less specific.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Khandekar | 2017-03-22 18:09:42 | Re: UPDATE of partition key |
| Previous Message | Simon Riggs | 2017-03-22 18:08:55 | Re: [PATCH] Transaction traceability - txid_status(bigint) |