X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 54F669FA278 for ; Fri, 19 May 2006 13:27:48 -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 87351-06 for ; Fri, 19 May 2006 13:27:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sand1.gxn.net (sand1.gxn.net [195.147.249.207]) by postgresql.org (Postfix) with ESMTP id A7A1C9FA22C for ; Fri, 19 May 2006 13:27:42 -0300 (ADT) Received: from [62.232.55.118] (helo=[192.168.0.2]) by sand1.gxn.net with esmtp (Exim 4.50) id 1Fh7s1-0005ow-Bl; Fri, 19 May 2006 17:30:33 +0100 Subject: Re: [ADMIN] does wal archiving block the current client connection? From: Simon Riggs To: Tom Lane Cc: Jeff Frost , pgsql-hackers@postgreSQL.org In-Reply-To: <727.1148054597@sss.pgh.pa.us> References: <727.1148054597@sss.pgh.pa.us> Content-Type: text/plain Date: Fri, 19 May 2006 17:27:33 +0100 Message-Id: <1148056053.2646.672.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/743 X-Sequence-Number: 83608 On Fri, 2006-05-19 at 12:03 -0400, Tom Lane wrote: > Simon Riggs writes: > > OK, I'm on it. > > What solution have you got in mind? I was thinking about an fcntl lock > to ensure only one archiver is active in a given data directory. That > would fix the problem without affecting anything outside the archiver. > Not sure what's the most portable way to do it though. I was trying to think of a better way than using an archiver.pid file in pg_xlog/archive_status... -- Simon Riggs EnterpriseDB http://www.enterprisedb.com