| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: does wal archiving block the current client connection? |
| Date: | 2006-05-19 16:41:40 |
| Message-ID: | 1148056900.2646.687.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-05-19 20:00:57 | Re: query optimization - mysql vs postgresql |
| Previous Message | Jeff Frost | 2006-05-19 16:36:47 | Re: does wal archiving block the current client connection? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Ellsworth | 2006-05-19 16:42:49 | Re: [HACKERS] Toward A Positive Marketing Approach. |
| Previous Message | Jeff Frost | 2006-05-19 16:36:47 | Re: does wal archiving block the current client connection? |