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 D6D3B9FA682; Fri, 19 May 2006 13:21: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 88502-01; Fri, 19 May 2006 13:20:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- 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 8C3F29FA4F2; Fri, 19 May 2006 13:20:56 -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 k4JGKkpk001942; Fri, 19 May 2006 12:20:46 -0400 (EDT) To: Jeff Frost , Simon Riggs , pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: does wal archiving block the current client connection? In-reply-to: <1879.1148055449@sss.pgh.pa.us> References: <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> <1879.1148055449@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Fri, 19 May 2006 12:17:29 -0400" Date: Fri, 19 May 2006 12:20:45 -0400 Message-ID: <1941.1148055645@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/275 X-Sequence-Number: 21807 I wrote: > Well, the fact that there's only one archiver *now* doesn't mean there > wasn't more than one when the problem happened. The orphaned archiver > would eventually quit. But, actually, nevermind: we have explained the failures you were seeing in the test setup, but a multiple-active-archiver situation still doesn't explain the original situation of incoming connections getting blocked. What I'd suggest is resuming the test after making sure you've killed off any old archivers, and seeing if you can make any progress on reproducing the original problem. We definitely need a multiple-archiver interlock, but I think that must be unrelated to your real problem. regards, tom lane