From 883a9659faf6e49e314b264ca32ed7645068a409 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Tue, 15 Feb 2011 12:02:53 -0500 Subject: Assorted corrections to the patch to add WAL receiver replies. Per reports from Fujii Masao. --- doc/src/sgml/config.sgml | 46 +++++++++++++++++++++++----------------------- 1 file changed, 23 insertions(+), 23 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index b6f8621278c..9505caf47a2 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1984,29 +1984,6 @@ SET ENABLE_SEQSCAN TO OFF; - - wal_receiver_status_interval (integer) - - wal_receiver_status_interval configuration parameter - - - - Specifies the minimum frequency, in seconds, for the WAL receiver - process on the standby to send information about replication progress - to the primary, where they can be seen using the - pg_stat_replication view. The standby will report - the last transaction log position it has written, the last position it - has flushed to disk, and the last position it has applied. Updates are - sent each time the write or flush positions changed, or at least as - often as specified by this parameter. Thus, the apply position may - lag slightly behind the true position. Setting this parameter to zero - disables status updates completely. This parameter can only be set in - the postgresql.conf file or on the server command line. - The default value is 10 seconds. - - - - vacuum_defer_cleanup_age (integer) @@ -2121,6 +2098,29 @@ SET ENABLE_SEQSCAN TO OFF; + + wal_receiver_status_interval (integer) + + wal_receiver_status_interval configuration parameter + + + + Specifies the minimum frequency, in seconds, for the WAL receiver + process on the standby to send information about replication progress + to the primary, where they can be seen using the + pg_stat_replication view. The standby will report + the last transaction log position it has written, the last position it + has flushed to disk, and the last position it has applied. Updates are + sent each time the write or flush positions changed, or at least as + often as specified by this parameter. Thus, the apply position may + lag slightly behind the true position. Setting this parameter to zero + disables status updates completely. This parameter can only be set in + the postgresql.conf file or on the server command line. + The default value is 10 seconds. + + + + -- cgit v1.2.3