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 4AF159FA4EA for ; Fri, 19 May 2006 13:03:37 -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 82927-06 for ; Fri, 19 May 2006 13:03:33 -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 48E489FA38E for ; Fri, 19 May 2006 13:03:32 -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 k4JG3H83000728; Fri, 19 May 2006 12:03:17 -0400 (EDT) To: Simon Riggs cc: Jeff Frost , pgsql-hackers@postgreSQL.org Subject: Re: [ADMIN] does wal archiving block the current client connection? In-reply-to: <1148054357.2646.662.camel@localhost.localdomain> References: Comments: In-reply-to Simon Riggs message dated "Fri, 19 May 2006 16:59:17 +0100" Date: Fri, 19 May 2006 12:03:17 -0400 Message-ID: <727.1148054597@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/729 X-Sequence-Number: 83594 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. regards, tom lane