Message-ID: <52D86D65.5010000@joh.to>
Date: Fri, 17 Jan 2014 00:38:13 +0100
From: Marko Tiikkaja <marko@joh.to>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: pgsql-docs@postgresql.org
Subject: hot_standby_feedback and max_standby_archive_delay
Content-Type: multipart/mixed; boundary="------------000900020202080903070309"
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

This is a multi-part message in MIME format.
--------------000900020202080903070309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

Myself and others found this statement in the documentation about 
$SUBJECT very confusing: "max_standby_archive_delay must be kept large 
in this case, because delayed WAL files might already contain entries 
that conflict with the desired standby queries.".  After a chat with 
Andres I've tried to make it clearer what said statement tries to convey.

Did I succeed?


Regards,
Marko Tiikkaja

--------------000900020202080903070309
Content-Type: text/plain; charset=UTF-8; x-mac-type="0"; x-mac-creator="0";
 name="hot_standby_feedback.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="hot_standby_feedback.patch"

*** a/doc/src/sgml/high-availability.sgml
--- b/doc/src/sgml/high-availability.sgml
***************
*** 1810,1818 **** if (!triggered)
      situation will be no worse than if the standby queries were running
      directly on the primary server, and you are still getting the benefit of
      off-loading execution onto the standby.
!     <varname>max_standby_archive_delay</> must be kept large in this case,
!     because delayed WAL files might already contain entries that conflict with
!     the desired standby queries.
     </para>
  
     <para>
--- 1810,1820 ----
      situation will be no worse than if the standby queries were running
      directly on the primary server, and you are still getting the benefit of
      off-loading execution onto the standby.
!     If a standby loses connectivity to the master, its
!     <varname>hot_standby_feedback</> value is not respected by the master until
!     the connection has been restored.  If the slave wishes to continue
!     executing queries in that case, its <varname>max_standby_archive_delay</>
!     should be kept large.
     </para>
  
     <para>

--------------000900020202080903070309
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

--------------000900020202080903070309--