diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-03-02 20:17:45 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-03-02 20:17:48 -0500 |
commit | ee28cacf619f4d9c23af5a80e1171a5adae97381 (patch) | |
tree | dda36f982a797351cb56e3baf188a775f985512a /src/backend/tcop/postgres.c | |
parent | 57e6db706e81fd2609fa385677e6ae72471822fe (diff) | |
download | postgresql-ee28cacf619f4d9c23af5a80e1171a5adae97381.tar.gz postgresql-ee28cacf619f4d9c23af5a80e1171a5adae97381.zip |
Extend the abilities of libpq's target_session_attrs parameter.
In addition to the existing options of "any" and "read-write", we
now support "read-only", "primary", "standby", and "prefer-standby".
"read-write" retains its previous meaning of "transactions are
read-write by default", and "read-only" inverts that. The other
three modes test specifically for hot-standby status, which is not
quite the same thing. (Setting default_transaction_read_only on
a primary server renders it read-only to this logic, but not a
standby.)
Furthermore, if talking to a v14 or later server, no extra network
round trip is needed to detect the session's status; the GUC_REPORT
variables delivered by the server are enough. When talking to an
older server, a SHOW or SELECT query is issued to detect session
read-only-ness or server hot-standby state, as needed.
Haribabu Kommi, Greg Nancarrow, Vignesh C, Tom Lane; reviewed at
various times by Laurenz Albe, Takayuki Tsunakawa, Peter Smith.
Discussion: https://postgr.es/m/CAF3+xM+8-ztOkaV9gHiJ3wfgENTq97QcjXQt+rbFQ6F7oNzt9A@mail.gmail.com
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions