X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 7CDF19FA2FA for ; Fri, 19 May 2006 12:59:36 -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 82600-05 for ; Fri, 19 May 2006 12:59:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sand1.gxn.net (sand1.gxn.net [195.147.249.207]) by postgresql.org (Postfix) with ESMTP id 328D19FA0DA for ; Fri, 19 May 2006 12:59:26 -0300 (ADT) Received: from [62.232.55.118] (helo=[192.168.0.2]) by sand1.gxn.net with esmtp (Exim 4.50) id 1Fh7Qd-0004Ly-AE; Fri, 19 May 2006 17:02:15 +0100 Subject: Re: does wal archiving block the current client connection? From: Simon Riggs To: Jeff Frost Cc: Tom Lane , pgsql-admin@postgresql.org In-Reply-To: References: <1147781287.2646.32.camel@localhost.localdomain> <15699.1147840569@sss.pgh.pa.us> <1147858398.2646.150.camel@localhost.localdomain> <19436.1147874478@sss.pgh.pa.us> <7583.1147922685@sss.pgh.pa.us> <8269.1147927511@sss.pgh.pa.us> <1147942877.2646.388.camel@localhost.localdomain> <1148041593.2646.592.camel! @localhost.loca{ h@ | <578.1148053758@sss.pgh.pa.us> Content-Type: text/plain Date: Fri, 19 May 2006 16:59:17 +0100 Message-Id: <1148054357.2646.662.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/322 X-Sequence-Number: 21854 On Fri, 2006-05-19 at 08:53 -0700, Jeff Frost wrote: > On Fri, 19 May 2006, Tom Lane wrote: > > > Jeff Frost writes: > >> Do you think the postmaster on 5432 is trying to archive the other > >> postmaster's WAL files somehow? > > > > Not as long as they aren't in the same data directory ;-). What Simon > > was wondering about was whether an archiver process had somehow been > > left over from a previous incarnation of the test postmaster. The thing > > to do is look through "ps auxww" (or local equivalent) and see if you > > see more than one thing calling itself an archiver process. > > > > (Whether or not this explains Jeff's problem, it definitely seems like > > a failure mode that we need to guard against. We go to great lengths > > to prevent a new postmaster from starting when there are still live > > backends from a previous postmaster, but I don't think that interlock > > is effective for the archiver.) > > Well now, will you look at this: > > postgres 20228 1 0 May17 ? 00:00:00 postgres: archiver process > postgres 20573 1 0 May17 ? 00:00:00 postgres: archiver process > postgres 23817 23810 0 May17 pts/11 00:00:00 postgres: archiver process > > 23810 is the running postmaster: > > postgres 23810 1 0 May17 pts/11 00:03:01 /usr/local/pgsql-8.1.3/bin/postm > > do you think that got left around the last time I did a pg_ctl restart? OK, I'm on it. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com