Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1USrSr-0005AK-GR for pgsql-admin@arkaria.postgresql.org; Thu, 18 Apr 2013 16:13:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1USrSq-0000i9-NL for pgsql-admin@arkaria.postgresql.org; Thu, 18 Apr 2013 16:13:36 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1USrSp-0000i3-LI for pgsql-admin@postgresql.org; Thu, 18 Apr 2013 16:13:35 +0000 Received: from asbnvacz-mailrelay01.megapath.net ([207.145.128.243]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1USrSl-000178-Bj for pgsql-admin@postgresql.org; Thu, 18 Apr 2013 16:13:34 +0000 Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.39]) by asbnvacz-mailrelay01.megapath.net (Postfix) with ESMTP id BBBB71EE5151 for ; Thu, 18 Apr 2013 12:13:29 -0400 (EDT) Received: (qmail 23008 invoked from network); 18 Apr 2013 16:13:29 -0000 Received: by simscan 1.4.0 ppid: 12709, pid: 5920, t: 0.2260s scanners: clamav: m: Received: from unknown (HELO [192.168.2.133]) (sribe@elevated-dev.com@[205.170.118.129]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 18 Apr 2013 16:13:29 -0000 Subject: Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Scott Ribe In-Reply-To: <2C0926ABD16BB641A8E2F11A549200423DDBC79BF2@PHXCCRPRD01.adprod.bmc.com> Date: Thu, 18 Apr 2013 10:13:27 -0600 Cc: pgsql-admin@postgresql.org, "Zucker, Yehudit" , "Abraham, Danny" , "Miller, Moshe" Content-Transfer-Encoding: quoted-printable Message-Id: References: <2C0926ABD16BB641A8E2F11A549200423DDBC79BF2@PHXCCRPRD01.adprod.bmc.com> To: "Sofer, Yuval" X-Mailer: Apple Mail (2.1085) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail1.sea5 X-Spam-Level: X-Spam-Status: No, score=0.0 required=8.0 tests=none autolearn=disabled version=3.0.4 X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On Apr 18, 2013, at 9:40 AM, Sofer, Yuval wrote: > 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 = stuck because of unavailable secondary Postgres? No, that's what synchronous means. What you're describing is asynchronous, = and it seems like you should consider using asynchronous replication. --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin