Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 7BC49B5DBD0 for ; Tue, 23 Aug 2011 05:49:52 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 08924-06 for ; Tue, 23 Aug 2011 08:49:45 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mail.postgresql.org (Postfix) with ESMTP id 45A48B5D803 for ; Tue, 23 Aug 2011 05:49:44 -0300 (ADT) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Qvmg2-0002J5-Mc for pgsql-admin@postgresql.org; Tue, 23 Aug 2011 01:49:42 -0700 Date: Tue, 23 Aug 2011 01:49:42 -0700 (PDT) From: alexondi To: pgsql-admin@postgresql.org Message-ID: <1314089382271-4726014.post@n5.nabble.com> In-Reply-To: References: <1311279255.75976.YahooMailNeo@web120016.mail.ne1.yahoo.com> <1311351085.55818.YahooMailNeo@web120018.mail.ne1.yahoo.com> Subject: Re: replication_timeout does not seem to be working MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.058 tagged_above=-10 required=5 tests=BAYES_00=-1.9, SARE_SPEC_REPLICA=0.72, URI_HEX=1.122 X-Spam-Level: X-Archive-Number: 201108/196 X-Sequence-Number: 38183 >If no reply is returned from the standby in replication_timeout, the master thinks >that the connected standby is inactive, and terminates the replication connection. >This is useful for the master to detect a standby crash or network outage. After that master commit current transaction with "local" synchronous_commit or rollback? And why I setup this parameter replication_timeout = 2s and my wal's thread (on master and server are restarted within 2s)? -- View this message in context: http://postgresql.1045698.n5.nabble.com/replication-timeout-does-not-seem-to-be-working-tp4620827p4726014.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com.