From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Elvis Pranskevichus <elprans(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable. |
Date: | 2017-05-24 22:20:59 |
Message-ID: | 3091.1495664459@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, May 24, 2017 at 3:16 AM, Tsunakawa, Takayuki
> <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> wrote:
>> For this, I added a GUC_REPORT variable session_read_only which indicates the session's default read-only status. The characteristics are:
>>
>> * It cannot be changed directly by the user (postgresql.conf, SET, etc.)
>> * Its value is the same as default_transaction_read_only when not in recovery.
I didn't look at exactly how you tried to do that, but GUCs whose values
depend on other GUCs generally don't work well at all.
>> * Its value is false during recovery.
[ scratches head... ] Surely this should read as "true" during recovery?
Also, what happens if the standby server goes live mid-session?
>> Could you include this in PG 10?
I concur with Robert that this is too late for v10, and the argument to
shove it in anyway is not compelling.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-05-24 23:04:25 | Re: Improvement in log message of logical replication worker |
Previous Message | Robert Haas | 2017-05-24 22:09:21 | Re: [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable. |