Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id C4954B5D800 for ; Wed, 27 Jul 2011 04:12:07 -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 08943-04 for ; Wed, 27 Jul 2011 07:12:00 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.postgresql.org (Postfix) with ESMTP id 36B33B5DBCE for ; Wed, 27 Jul 2011 04:12:00 -0300 (ADT) Received: from [192.168.1.7] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu4) with ESMTP (Nemesis) id 0MEg2P-1Qf34Z1rE9-00FifP; Wed, 27 Jul 2011 08:47:02 +0200 Message-ID: <4E2FB465.90406@2ndQuadrant.com> Date: Wed, 27 Jul 2011 02:47:01 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110505 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: replication_timeout does not seem to be working References: <1311279255.75976.YahooMailNeo@web120016.mail.ne1.yahoo.com> <1311351085.55818.YahooMailNeo@web120018.mail.ne1.yahoo.com> In-Reply-To: <1311351085.55818.YahooMailNeo@web120018.mail.ne1.yahoo.com> Content-Type: multipart/alternative; boundary="------------020106010204060500020103" X-Provags-ID: V02:K0:eFDpmTisSmyPqrwd5T3QC828j0oPEfZ0z4a5K0WwQUW Wv5xfGMr1BaeMBTtlwK6uNjXM+PccANs8GEJnyFdiGAxUy6wRN AOGCTjYF6fY4r+dt7bXmCIZgmpaMbTgSrEqcn7UulXQM0vyd7K G9hgdqn2GGXgY+wqMH2sCRXz1mIquAw8BhEQ1fmObz/aPC0QXG nBoSknALCSzv4N0TDsklxzouM8Hq+rfA9NSKdJ7A8o= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.179 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 201107/188 X-Sequence-Number: 37967 This is a multi-part message in MIME format. --------------020106010204060500020103 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 07/22/2011 12:11 PM, A J wrote: > Basically I wish my synchronous write transaction to not wait > indefinitely when the synchronous standby servers are not available. > But rather a response returned back to client that write could not be > successful, after trying for 'n' seconds. How can that be accomplished ? You might be able to get what you want here by setting statement_timeout to 'n' seconds when doing a write transaction. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us --------------020106010204060500020103 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 07/22/2011 12:11 PM, A J wrote:
Basically I wish my synchronous write transaction to not wait indefinitely when the synchronous standby servers are not available. But rather a response returned back to client that write could not be successful, after trying for 'n' seconds. How can that be accomplished ?

You might be able to get what you want here by setting statement_timeout to 'n' seconds when doing a write transaction.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us
--------------020106010204060500020103--