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 283739FA3A6 for ; Tue, 23 May 2006 12:09:45 -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 84960-02-2 for ; Tue, 23 May 2006 12:09:34 -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 C844E9FA425 for ; Tue, 23 May 2006 12:09:33 -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 k4NF9O3r005782; Tue, 23 May 2006 11:09:24 -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: <1148396461.2646.833.camel@localhost.localdomain> 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> <1148396461.2646.833.camel@localhost.localdomain> Comments: In-reply-to Simon Riggs message dated "Tue, 23 May 2006 16:01:01 +0100" Date: Tue, 23 May 2006 11:09:24 -0400 Message-ID: <5781.1148396964@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/923 X-Sequence-Number: 83788 Simon Riggs writes: > On Tue, 2006-05-23 at 10:53 -0400, Tom Lane wrote: >> 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. Postmaster crashes are not a problem in practice; we've been careful to keep the postmaster doing so little that there's no material risk of it failing. If the postmaster dies it's almost certainly because someone killed it, and you really want the child processes to close up shop too. (If we did want the archiver to keep running, it shouldn't have any PostmasterIsAlive check at all; I can't see a reason why completing one iteration of the outer loop is a better time to stop than any other time.) regards, tom lane