This allows clients to find out the setting at connection time without
having to expend a query round trip to do so; which is helpful when
trying to identify read/write servers. (One must also look at
in_hot_standby, but that's already GUC_REPORT, cf
bf8a662c9.)
Modifying libpq to make use of this will come soon, but I felt it
cleaner to push the server change separately.
Haribabu Kommi, Greg Nancarrow, Vignesh C; reviewed at various times
by Laurenz Albe, Takayuki Tsunakawa, Peter Smith.
Discussion: https://postgr.es/m/CAF3+xM+8-ztOkaV9gHiJ3wfgENTq97QcjXQt+rbFQ6F7oNzt9A@mail.gmail.com
server_encoding,
client_encoding,
application_name,
+ default_transaction_read_only,
in_hot_standby,
is_superuser,
session_authorization,
IntervalStyle was not reported by releases before 8.4;
application_name was not reported by releases before
9.0;
- in_hot_standby was not reported by releases before
+ default_transaction_read_only and
+ in_hot_standby were not reported by releases before
14.)
Note that
server_version,
server_encoding,
client_encoding,
application_name,
+ default_transaction_read_only,
in_hot_standby,
is_superuser,
session_authorization,
IntervalStyle was not reported by releases before 8.4;
application_name was not reported by releases before
9.0;
- in_hot_standby was not reported by releases before
+ default_transaction_read_only and
+ in_hot_standby were not reported by releases before
14.)
Note that
server_version,
{
{"default_transaction_read_only", PGC_USERSET, CLIENT_CONN_STATEMENT,
gettext_noop("Sets the default read-only status of new transactions."),
- NULL
+ NULL,
+ GUC_REPORT
},
&DefaultXactReadOnly,
false,