X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id AE09B9FA2C8; Fri, 19 May 2006 13:25:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 89160-04; Fri, 19 May 2006 13:25:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sand4.gxn.net (sand4.gxn.net [195.147.249.239]) by postgresql.org (Postfix) with ESMTP id 2F1B49FA22C; Fri, 19 May 2006 13:25:36 -0300 (ADT) Received: from [62.232.55.118] (helo=[192.168.0.2]) by sand4.gxn.net with esmtp (Exim 4.50) id 1Fh7ll-0000Vb-OC; Fri, 19 May 2006 17:24:05 +0100 Subject: Re: does wal archiving block the current client connection? From: Simon Riggs To: Tom Lane Cc: Jeff Frost , pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org In-Reply-To: <1941.1148055645@sss.pgh.pa.us> References: <15699.1147840569@sss.pgh.pa.us> <1147858398.2646.150.camel@localhost.localdomain> <19436.1147874478@sss.pgh.pa.us> <7583.1147922685@sss.pgh.pa.us> <8269.1147927511@sss.pgh.pa.us> <1879.1148055449@sss.pgh.pa.us> <1941.1148055645@sss.pgh.pa.us> Content-Type: text/plain Date: Fri, 19 May 2006 17:25:31 +0100 Message-Id: <1148055931.2646.669.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/276 X-Sequence-Number: 21808 On Fri, 2006-05-19 at 12:20 -0400, Tom Lane wrote: > I wrote: > > Well, the fact that there's only one archiver *now* doesn't mean there > > wasn't more than one when the problem happened. The orphaned archiver > > would eventually quit. > > But, actually, nevermind: we have explained the failures you were seeing > in the test setup, but a multiple-active-archiver situation still > doesn't explain the original situation of incoming connections getting > blocked. Agreed. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com