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 7F2B29FA22C; Fri, 19 May 2006 13:41:55 -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 91718-02; Fri, 19 May 2006 13:41:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- 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 38C979FA278; Fri, 19 May 2006 13:41:45 -0300 (ADT) Received: from [62.232.55.118] (helo=[192.168.0.2]) by sand1.gxn.net with esmtp (Exim 4.50) id 1Fh85b-0006bv-Rw; Fri, 19 May 2006 17:44:35 +0100 Subject: Re: does wal archiving block the current client connection? From: Simon Riggs To: Jeff Frost Cc: Tom Lane , pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org In-Reply-To: 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> <1941.1148055645@sss.pgh.pa.us> Content-Type: text/plain Date: Fri, 19 May 2006 17:41:40 +0100 Message-Id: <1148056900.2646.687.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/279 X-Sequence-Number: 21811 On Fri, 2006-05-19 at 09:36 -0700, Jeff Frost wrote: > On Fri, 19 May 2006, Tom Lane wrote: > > > 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. > > Ok, so I've got the old archivers gone (and btw, after a restart I ended up > with 3 of them - so I stopped postmaster, and killed them all individually and > started postmaster again). Thats good. > Now I can run my same pg_bench, or do you guys > have any other suggestions on attempting to reproduce the problem? No. We're back on track to try to reproduce the original error. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com