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 2EDD89FA226 for ; Wed, 17 May 2006 11:01:42 -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 19790-08 for ; Wed, 17 May 2006 11:01:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 581C89F9C18 for ; Wed, 17 May 2006 11:01:31 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4HE1IGs019437; Wed, 17 May 2006 10:01:18 -0400 (EDT) To: Simon Riggs cc: Jeff Frost , pgsql-admin@postgresql.org Subject: Re: does wal archiving block the current client connection? In-reply-to: <1147858398.2646.150.camel@localhost.localdomain> 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> Comments: In-reply-to Simon Riggs message dated "Wed, 17 May 2006 10:33:18 +0100" Date: Wed, 17 May 2006 10:01:18 -0400 Message-ID: <19436.1147874478@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/233 X-Sequence-Number: 21765 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 > The "lurking feeling" scenario above might or might nor be an issue > here, but I can't see how the archiver could be involved at all. Well, I don't see it either; at this point we're waiting on Jeff to provide some harder evidence ... regards, tom lane