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 66B399FA226 for ; Wed, 17 May 2006 11:41:02 -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 27033-09 for ; Wed, 17 May 2006 11:40:51 -0300 (ADT) 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 6EF539F9C18 for ; Wed, 17 May 2006 11:40:51 -0300 (ADT) Received: from [62.232.55.118] (helo=[192.168.0.2]) by sand4.gxn.net with esmtp (Exim 4.50) id 1FgNB9-000779-HM; Wed, 17 May 2006 15:39:11 +0100 Subject: Re: does wal archiving block the current client connection? From: Simon Riggs To: Tom Lane Cc: Jeff Frost , pgsql-admin@postgresql.org In-Reply-To: <19436.1147874478@sss.pgh.pa.us> References: <1147728181.5074.73.camel@localhost.localdomain> <1147733193.5074.87.camel@localhost.localdomain> <1147781287.2646.32.camel@localhost.localdomain> <15699.1147840569@sss.pgh.pa.us> <1147858398.2646.150.camel@localhost.localdomain> <19436.1147874478@sss.pgh.pa.us> Content-Type: text/plain Date: Wed, 17 May 2006 15:40:35 +0100 Message-Id: <1147876835.2646.227.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/234 X-Sequence-Number: 21766 On Wed, 2006-05-17 at 10:01 -0400, Tom Lane wrote: > Simon Riggs writes: > > You'll have to explain a little more. I checked the archives... > > I was thinking of > http://archives.postgresql.org/pgsql-hackers/2004-01/msg00530.php > full explanation here: > http://archives.postgresql.org/pgsql-hackers/2004-01/msg00606.php Sorry, I see my note looks like I couldn't find it. I meant "I've read the archives". Thanks though. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com