Re: does wal archiving block the current client connection? - Mailing list pgsql-admin

From Simon Riggs
Subject Re: does wal archiving block the current client connection?
Date
Msg-id 1148056900.2646.687.camel@localhost.localdomain
Whole thread Raw
In response to Re: does wal archiving block the current client connection?  (Jeff Frost <jeff@frostconsultingllc.com>)
Responses Re: does wal archiving block the current client connection?
List pgsql-admin
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


pgsql-admin by date:

Previous
From: Jeff Frost
Date:
Subject: Re: does wal archiving block the current client connection?
Next
From: Alvaro Herrera
Date:
Subject: Re: query optimization - mysql vs postgresql