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 CD3029FA3AD for ; Fri, 19 May 2006 12:49:41 -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 80416-09 for ; Fri, 19 May 2006 12:49: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 3C9499F9AFD for ; Fri, 19 May 2006 12:49:34 -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 k4JFnIBc000579; Fri, 19 May 2006 11:49:18 -0400 (EDT) To: Jeff Frost cc: Simon Riggs , pgsql-admin@postgresql.org Subject: Re: does wal archiving block the current client connection? In-reply-to: References: <1147728181.5074.73.camel@localhost.localdomain> <1147733193.5074.87.camel@localhost.localdomain> <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@ | Comments: In-reply-to Jeff Frost message dated "Fri, 19 May 2006 08:23:11 -0700" Date: Fri, 19 May 2006 11:49:18 -0400 Message-ID: <578.1148053758@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/324 X-Sequence-Number: 21856 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.) regards, tom lane