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 418899FA3A6 for ; Tue, 23 May 2006 11:54:06 -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-03 for ; Tue, 23 May 2006 11:53:55 -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 4D5DE9F946D for ; Tue, 23 May 2006 11:53:55 -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 k4NErlgv003836; Tue, 23 May 2006 10:53:47 -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: <1148395755.2646.825.camel@localhost.localdomain> References: <727.1148054597@sss.pgh.pa.us> <1148056053.2646.672.camel@localhost.localdomain> <1148395755.2646.825.camel@localhost.localdomain> Comments: In-reply-to Simon Riggs message dated "Tue, 23 May 2006 15:49:15 +0100" Date: Tue, 23 May 2006 10:53:47 -0400 Message-ID: <3835.1148396027@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/920 X-Sequence-Number: 83785 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. regards, tom lane