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 72A409FA3A6 for ; Tue, 23 May 2006 12:01:29 -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 81696-08 for ; Tue, 23 May 2006 12:01:16 -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 0173B9F94EA for ; Tue, 23 May 2006 12:01:13 -0300 (ADT) Received: from [62.232.55.118] (helo=[192.168.0.2]) by sand4.gxn.net with esmtp (Exim 4.50) id 1FiYMD-0000aV-4b; Tue, 23 May 2006 15:59:37 +0100 Subject: Re: [ADMIN] does wal archiving block the current client From: Simon Riggs To: Tom Lane Cc: Jeff Frost , pgsql-hackers@postgreSQL.org In-Reply-To: <3835.1148396027@sss.pgh.pa.us> References: <727.1148054597@sss.pgh.pa.us> <1148056053.2646.672.camel@localhost.localdomain> <1148395755.2646.825.camel@localhost.localdomain> <3835.1148396027@sss.pgh.pa.us> Content-Type: text/plain Date: Tue, 23 May 2006 16:01:01 +0100 Message-Id: <1148396461.2646.833.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/922 X-Sequence-Number: 83787 On Tue, 2006-05-23 at 10:53 -0400, Tom Lane wrote: > Simon Riggs writes: > > This doesn't quite get to the nub of the problem: archiver is designed > > to keep archiving files, even in the event that the postmaster explodes. > > It will keep archiving until they're all gone. > > I think we just need a PostmasterIsAlive check in the per-file loop. ...which would mean the archiver would not outlive postmaster in the event it crashes...which is exactly the time you want it to keep going. Granted, that's an easy change. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com