| From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, 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:36:47 |
| Message-ID: | Pine.LNX.4.64.0605190933310.7012@discord.home.frostconsultingllc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
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). Now I can run my same pg_bench, or do you guys
have any other suggestions on attempting to reproduce the problem?
--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-05-19 16:41:40 | Re: does wal archiving block the current client connection? |
| Previous Message | Jeff Frost | 2006-05-19 16:32:42 | Re: does wal archiving block the current client connection? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-05-19 16:41:40 | Re: does wal archiving block the current client connection? |
| Previous Message | Jeff Frost | 2006-05-19 16:32:42 | Re: does wal archiving block the current client connection? |