Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id A0096B5DBC5 for ; Fri, 22 Jul 2011 13:11:33 -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 32416-08 for ; Fri, 22 Jul 2011 16:11:27 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nm16-vm1.bullet.mail.ne1.yahoo.com (nm16-vm1.bullet.mail.ne1.yahoo.com [98.138.91.47]) by mail.postgresql.org (Postfix) with SMTP id 28C56B5D8C5 for ; Fri, 22 Jul 2011 13:11:26 -0300 (ADT) Received: from [98.138.90.53] by nm16.bullet.mail.ne1.yahoo.com with NNFMP; 22 Jul 2011 16:11:26 -0000 Received: from [98.138.89.196] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 22 Jul 2011 16:11:25 -0000 Received: from [127.0.0.1] by omp1054.mail.ne1.yahoo.com with NNFMP; 22 Jul 2011 16:11:25 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 971811.12361.bm@omp1054.mail.ne1.yahoo.com Received: (qmail 55992 invoked by uid 60001); 22 Jul 2011 16:11:25 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1311351085; bh=P4ZY14o0O9S9xOU2DeVetz97KwMzeyYKHTDBRbNo6CY=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=bBin8t/g2Bj284M6GpRybROv5EYiKSOJg6Z/HnCFH8POj0+bwKv2zIrqux2Bo7GnRH3fdQrmsln5CoXAo3AhT3oCYGGUnZELS5cnYSNX8Gr0IGeczwOXyOl2CL6PPgP3rKu8Ect4YY53lSv8SUVWJ7X4U1cp52jVRWwFSp2FeqE= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=V9uASuZ4vi5AckrjCE0FvzYNGs2Q1NE5XeKGiPmnY1763eX4AEncYgr4oQXfahmY4OBXNRLoPekOS3X9rctogpwrLh0dSDwkOY8uWgwpX9Q+aNdg0+UEzgpI6NVg8JOrp1sCFSc8FVGM/3T5hC3tM77IxXo4JCUTdBjy1qNOlcQ=; X-YMail-OSG: MSazkdUVM1nJ073qPaPirBuGV5awCb7bqTUdjoZdzUI9oAe GKZccTc0XWACkuTxP81NXNetoV8aqVXwkQ_XlswUm9C0KXXPN776ORov0IA7 _bT5gf79iRA5Cask8A6vfscwiklooB4Dszo_3g4dl8QivglbAZB24GqVqKvC eW5XXdceZTHFxRA8mwjNjBcllk42rbWnuTNVlP_vBHx2P4BBpxogOmXmJZED AHB8iEJpwe0iAYBMpBz7tB.zbVq1lZKT595r4tsPyOJjrx8gw9fmCfQnAGL6 hJyHrjnpTue09QEpHn.dfm.1V1oemQiFY53l7ThJcFs8xJVbL9cs- Received: from [64.61.91.74] by web120018.mail.ne1.yahoo.com via HTTP; Fri, 22 Jul 2011 09:11:25 PDT X-Mailer: YahooMailWebService/0.8.112.310352 References: <1311279255.75976.YahooMailNeo@web120016.mail.ne1.yahoo.com> Message-ID: <1311351085.55818.YahooMailNeo@web120018.mail.ne1.yahoo.com> Date: Fri, 22 Jul 2011 09:11:25 -0700 (PDT) From: A J Reply-To: A J Subject: Re: replication_timeout does not seem to be working To: Fujii Masao Cc: PG Admin In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-2105355445-1311351085=:55818" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.24 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, FS_REPLICA=3.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.181, SARE_SPEC_REPLICA=0.72 X-Spam-Level: * X-Archive-Number: 201107/171 X-Sequence-Number: 37950 --0-2105355445-1311351085=:55818 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I am still not clear. Can you explain what replication_timeout parameter ac= complishes and when ?=0A=0ABasically I wish my synchronous write transactio= n to not wait indefinitely when the synchronous standby servers are not ava= ilable. But rather a response returned back to client that write could not = be successful, after trying for 'n' seconds. How can that be accomplished ?= =0A=0AThanks.=0A=0A=0A=0A=0A________________________________=0AFrom: Fujii = Masao =0ATo: A J =0ACc: PG Admin =0ASent: Friday, July 22, 2011 9:19 AM=0ASubject:= Re: [ADMIN] replication_timeout does not seem to be working=0A=0AOn Fri, J= ul 22, 2011 at 5:14 AM, A J wrote:=0A> On 9.1, Beta3 I se= t the following on master=0A> replication_timeout =3D 10s =A0 =A0 =A0 # in = milliseconds; 0 disables=0A> With no slaves running, I expect a failure in = about 10s. But any Insert just=0A> hangs. Any idea ?=0A=0AIf you set up syn= chronous replication but there is no standby server,=0Aall the write transa= ctions are blocked infinitely whether replication_timeout=0Ais enabled or n= ot. If you want to cause those transactions to end, you need=0Ato disable s= ynchronous replication by, for example, emptying=0Asynchronous_standby_name= s or need to set up new standby.=0A=0ARegards,=0A=0A-- =0AFujii Masao=0ANIP= PON TELEGRAPH AND TELEPHONE CORPORATION=0ANTT Open Source Software Center --0-2105355445-1311351085=:55818 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
I am still= not clear. Can you explain what replication_timeout parameter accomplishes= and when ?

Basically I = wish my synchronous write transaction to not wait indefinitely when the syn= chronous standby servers are not available. But rather a response returned = back to client that write could not be successful, after trying for 'n' sec= onds. How can that be accomplished ?

Thanks.


From: Fujii Masao <masao.fujii@g= mail.com>
To: A J &l= t;s5aly@yahoo.com>
Cc: PG Admin <pgsql-admin@postgresql.org>
Sent: Friday, July 22, 2011 9:19 AM
Subject: Re: [ADMIN] replication_timeo= ut does not seem to be working

On Fri, Jul 22, 2011 at 5:14 A= M, A J <s5aly@yahoo.com> wrote:
> On 9.1, Beta3 I set the follow= ing on master
> replication_timeout =3D 10s       # in= milliseconds; 0 disables
> With no slaves running, I expect a failur= e in about 10s. But any Insert just
> hangs. Any idea ?

If you= set up synchronous replication but there is no standby server,
all the = write transactions are blocked infinitely whether replication_timeout
is enab= led or not. If you want to cause those transactions to end, you need
to = disable synchronous replication by, for example, emptying
synchronous_st= andby_names or need to set up new standby.

Regards,

--
Fu= jii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source = Software Center


--0-2105355445-1311351085=:55818--