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 8924D9FA3A6 for ; Tue, 23 May 2006 12:26:56 -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 87827-03 for ; Tue, 23 May 2006 12:26:50 -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 1F78D9F946D for ; Tue, 23 May 2006 12:26:49 -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 k4NFQip8008769; Tue, 23 May 2006 11:26:44 -0400 (EDT) To: Simon Riggs cc: Jeff Frost , pgsql-hackers@postgresql.org Subject: Re: [ADMIN] does wal archiving block the current client 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 11:26:44 -0400 Message-ID: <8768.1148398004@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/928 X-Sequence-Number: 83793 Simon Riggs writes: > My recent patch will prevent server startup, so if you do a fast restart > to bounce the server and change parameters you'll have to keep the > server down while the archiver completes (or you kill it). BTW, I was not planning on having it do that. The archiver subprocess should fail to start (and the PM keep trying to start it). Not take down the entire database. regards, tom lane