From Yuval_Sofer@bmc.com Thu Apr 18 15:41:42 2013 Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1USqxy-0001YM-M6 for pgsql-sql@arkaria.postgresql.org; Thu, 18 Apr 2013 15:41:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1USqxx-0000gn-HJ for pgsql-sql@arkaria.postgresql.org; Thu, 18 Apr 2013 15:41:41 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1USqxn-0000YC-5j for pgsql-sql@postgresql.org; Thu, 18 Apr 2013 15:41:31 +0000 Received: from rubyred.bmc.com ([198.147.195.5] helo=flicker.bmc.com) by makus.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1USqxg-0000bb-LH for pgsql-sql@postgresql.org; Thu, 18 Apr 2013 15:41:30 +0000 Received: from phx-htprd-03.adprod.bmc.com (phx-htprd-03.adprod.bmc.com [172.24.32.133]) by flicker.bmc.com (Postfix) with ESMTP id 9A3E01E9ACE for ; Thu, 18 Apr 2013 10:44:19 -0500 (CDT) Received: from PHXCCRPRD01.adprod.bmc.com ([172.24.32.6]) by phx-htprd-03.adprod.bmc.com ([172.24.31.107]) with mapi; Thu, 18 Apr 2013 10:41:24 -0500 From: "Sofer, Yuval" To: "pgsql-sql@postgresql.org" CC: "Zucker, Yehudit" , "Abraham, Danny" , "Miller, Moshe" Date: Thu, 18 Apr 2013 10:41:22 -0500 Subject: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Thread-Topic: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Thread-Index: Ac48Sy1VfVbfSslZSSKh6lLqUxF2uw== Message-ID: <2C0926ABD16BB641A8E2F11A549200423DDBC79BF6@PHXCCRPRD01.adprod.bmc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_2C0926ABD16BB641A8E2F11A549200423DDBC79BF6PHXCCRPRD01ad_" MIME-Version: 1.0 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org --_000_2C0926ABD16BB641A8E2F11A549200423DDBC79BF6PHXCCRPRD01ad_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I am using Postgres DB with stand by database, configured with streaming in= synchronized mode (each commit on primary DB waits for commit on secondary= DB). Sometimes we suffer from network issues and as consequences, secondary mach= ine is not available. In these situations, our application is stuck and do not respond anymore, s= ince no confirmation comes from the secondary Postgres (obviously... it is = down or unavailable....). Is there any parameter that I can use, to enable recovering from hanging on= until someone of us re-establish connection to secondary DB? Maybe some configuration parameter that sets the time interval for being st= uck because of unavailable secondary Postgres? Please help, Thanks, Yuval Sofer BMC Software CTM&D Business Unit DBA Team 972-52-4286-282 yuval_sofer@bmc.com --_000_2C0926ABD16BB641A8E2F11A549200423DDBC79BF6PHXCCRPRD01ad_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 =

I am using Postgres DB with stand by database, configured with strea= ming in synchronized mode (each commit on primary DB waits for commit on se= condary DB).

 

Sometimes we suffer f= rom network issues and as consequences, secondary machine is not available.=

 

In these situations, our applicat= ion is stuck and do not respond anymore, since no confirmation comes from t= he secondary Postgres (obviously… it is down or unavailable….).=

 

Is there any parameter that I ca= n use, to enable recovering from hanging on until someone of us re-establis= h connection to secondary DB?

= Maybe some configuration par= ameter that sets the time interval for being stuck because of unavailable s= econdary Postgres?

 

Please help,=

 

Thanks,

&n= bsp;

 

Yuval S= ofer

BMC Software

DBA Team

972-52-4286-282

yuval_sofer@bmc.com

 

<= o:p> 

 

 

= --_000_2C0926ABD16BB641A8E2F11A549200423DDBC79BF6PHXCCRPRD01ad_-- From akretschmer@spamfence.net Thu Apr 18 16:38:24 2013 Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1USrqq-00083o-1h for pgsql-sql@arkaria.postgresql.org; Thu, 18 Apr 2013 16:38:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1USrqp-00069c-Br for pgsql-sql@arkaria.postgresql.org; Thu, 18 Apr 2013 16:38:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1USrqo-00069W-Ei for pgsql-sql@postgresql.org; Thu, 18 Apr 2013 16:38:22 +0000 Received: from mailout01.ims-firmen.de ([213.174.32.96]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1USrqh-0005E0-D7 for pgsql-sql@postgresql.org; Thu, 18 Apr 2013 16:38:22 +0000 Received: from mailin02.ims-firmen.de ([192.168.1.142]) by mailout01.ims-firmen.de with esmtp (envelope-from ) id 1USrqg-00075u-gi for pgsql-sql@postgresql.org; Thu, 18 Apr 2013 18:38:14 +0200 Received: from [87.170.181.36] (helo=a-kretschmer.de) by mailin02.ims-firmen.de with esmtpsa (TLSv1:AES256-SHA:256) (envelope-from ) id 1USrqg-0006Ci-3K for pgsql-sql@postgresql.org; Thu, 18 Apr 2013 18:38:14 +0200 Received: from kretschmer by a-kretschmer.de with local (Exim 4.69) (envelope-from ) id 1USrqe-0006Ip-U1 for pgsql-sql@postgresql.org; Thu, 18 Apr 2013 18:38:12 +0200 Date: Thu, 18 Apr 2013 18:38:12 +0200 From: Andreas Kretschmer To: pgsql-sql@postgresql.org Subject: Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Message-ID: <20130418163812.GA24028@tux> References: <2C0926ABD16BB641A8E2F11A549200423DDBC79BF6@PHXCCRPRD01.adprod.bmc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2C0926ABD16BB641A8E2F11A549200423DDBC79BF6@PHXCCRPRD01.adprod.bmc.com> X-OS: Debian/GNU Linux - weil ich es mir Wert bin! X-GPG-Fingerprint: EE16 3C01 7B9C 10F7 2C8B 3B86 4DB3 D9EE 7F45 84DA X-Message-Flag: "Windows" is not the answer. "Windows" is the question and the answer is "no"! X-Lugdd: Gerd Kube X-Info: My name is root. Just root. And I am licensed to kill -9 User-Agent: Mutt/1.5.18 (2008-05-17) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org Sofer, Yuval wrote: > Hi, > > > > I am using Postgres DB with stand by database, configured with streaming in > synchronized mode (each commit on primary DB waits for commit on secondary DB). > > > > Sometimes we suffer from network issues and as consequences, secondary machine > is not available. > > > > In these situations, our application is stuck and do not respond anymore, since > no confirmation comes from the secondary Postgres (obviously… it is down or > unavailable….). > > > > Is there any parameter that I can use, to enable recovering from hanging on > until someone of us re-establish connection to secondary DB? Use asynchronous mode. There is no way for 'only a little bit synchronized mode'. We are not in the mysql-world ... Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889° -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql