pgsql: Make GUC wal_sender_timeout user-settable

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Make GUC wal_sender_timeout user-settable
Date: 2018-09-22 06:26:29
Message-ID: E1g3bN7-0003zl-DK@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Make GUC wal_sender_timeout user-settable

Being able to use a value that can be changed on a connection basis is
useful with clusters distributed geographically, and makes failure
detection more flexible. A note is added in the documentation about the
use of "options" in primary_conninfo, which can be hard to grasp for
newcomers with the need of two single quotes when listing a set of
parameters.

Author: Tsunakawa Takayuki
Reviewed-by: Masahiko Sawada, Michael Paquier
Discussion: https://postgr.es/m/0A3221C70F24FB45833433255569204D1FAAD3AE@G01JPEXMBYT05

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/db361db2fce7491303f49243f652c75c084f5a19

Modified Files
--------------
doc/src/sgml/config.sgml | 12 ++++++++----
doc/src/sgml/high-availability.sgml | 2 +-
src/backend/utils/misc/guc.c | 2 +-
3 files changed, 10 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2018-09-22 13:27:50 pgsql: Replace CAS loop with single TAS in ProcArrayGroupClearXid()
Previous Message Tom Lane 2018-09-22 00:50:55 pgsql: Get rid of explicit argument-count markings in tab-complete.c.