Date: Thu, 18 Apr 2013 18:38:12 +0200
From: Andreas Kretschmer <akretschmer@spamfence.net>
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>
User-Agent: Mutt/1.5.18 (2008-05-17)
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Sofer, Yuval <Yuval_Sofer@bmc.com> 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