Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 7271F930E1E
	for <pgsql-docs@postgresql.org>; Fri,  3 Aug 2012 17:33:38 -0300 (ADT)
Received: from momjian.us ([72.94.173.45])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <bruce@momjian.us>) id 1SxOYx-0003Xe-UW
	for pgsql-docs@postgresql.org; Fri, 03 Aug 2012 20:33:37 +0000
Received: from bruce by momjian.us with local (Exim 4.72)
	(envelope-from <bruce@momjian.us>)
	id 1SxOYk-0000Ph-4r; Fri, 03 Aug 2012 16:33:22 -0400
Date: Fri, 3 Aug 2012 16:33:22 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Erik Rijkers <er@xs4all.nl>
Cc: pgsql-docs@postgresql.org
Subject: Re: pdf-visible links into config.gsml from
 high-availability.sgml
Message-ID: <20120803203322.GJ3463@momjian.us>
References: <2ca7db058d1f4a8af065b0b47ed1f3d7.squirrel@webmail.xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2ca7db058d1f4a8af065b0b47ed1f3d7.squirrel@webmail.xs4all.nl>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201208/1
X-Sequence-Number: 7394

On Tue, Jul 19, 2011 at 12:29:59PM +0200, Erik Rijkers wrote:
> 
> Reading about synchronous replication in a paper copy of .pdf high-availability.sgml pages, I
> missed the information in config.sgml. There /is/ a (single) link, but it's not visible in the
> pdf; even with the pdf on-screen it is only noticable only with MouseOver.
> 
> I think it would be good to make two explicit, visible links, as attached, to connect the two main
> places with sync-repl information.  Then there will be a clear "See Section ..." reference.
> 
> (against today's REL9_1_STABLE)
> 
> thanks,
> 
> Erik Rijkers

> --- doc/src/sgml/high-availability.sgml.orig	2011-07-19 11:23:06.000000000 +0200
> +++ doc/src/sgml/high-availability.sgml	2011-07-19 11:25:38.000000000 +0200
> @@ -935,7 +935,9 @@
>      <xref linkend="guc-synchronous-standby-names"> must be set to
>      a non-empty value.  <varname>synchronous_commit</> must also be set to
>      <literal>on</>, but since this is the default value, typically no change is
> -    required.  This configuration will cause each commit to wait for
> +    required. (See <xref linkend="runtime-config-wal-settings"> and 
> +    <xref linkend="runtime-config-replication-master">.)
> +    This configuration will cause each commit to wait for
>      confirmation that the standby has written the commit record to durable
>      storage, even if that takes a very long time.
>      <varname>synchronous_commit</> can be set by individual

OK, patch applied to 9.2 and head.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +