Re: Libpq support to connect to standby server as priority
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Haribabu Kommi <kommi.haribabu@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Jing Wang <jingwangian@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>, "Tsunakawa, Takayuki"
<tsunakawa.takay@jp.fujitsu.com>
Date: 2018-11-09T11:53:01Z
Lists: pgsql-hackers
Haribabu Kommi wrote: > Added comments along the lines that you mentioned. And also try > to update some more comments. Looks ok to me, I'll mark it as "ready for committer". Yours, Laurenz Albe
Commits
-
Make test_target_session_attrs more robust against connection failure.
- 3769e11a3183 14.0 landed
-
Extend the abilities of libpq's target_session_attrs parameter.
- ee28cacf619f 14.0 landed
-
Mark default_transaction_read_only as GUC_REPORT.
- d16f8c8e416d 14.0 landed
-
Introduce a new GUC_REPORT setting "in_hot_standby".
- bf8a662c9afa 14.0 landed
-
Avoid spamming the client with multiple ParameterStatus messages.
- 2432b1a04087 14.0 landed
-
Avoid harmless Valgrind no-buffer-pin errors.
- a766d6ca22ac 14.0 cited
-
Restructure libpq code to remove some duplicity
- b438e7e7a1c5 13.0 landed
-
libpq: Add target_session_attrs parameter.
- 721f7bd3cbcc 10.0 cited