| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
| 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:17:29 |
| Message-ID: | 1879.1148055449@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Jeff Frost <jeff(at)frostconsultingllc(dot)com> writes:
> Hurray! Unfortunately, the postmaster on the original troubled server almost
> never gets restarted, and in fact only has only one archiver process running
> right now. Drat!
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.
Do you have logs that would let you check when the production postmaster
was restarted?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-19 16:20:45 | Re: does wal archiving block the current client connection? |
| Previous Message | Jeff Frost | 2006-05-19 16:08:19 | Re: does wal archiving block the current client connection? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-19 16:20:45 | Re: does wal archiving block the current client connection? |
| Previous Message | Alvaro Herrera | 2006-05-19 16:15:38 | Re: [OT] MySQL is bad, but THIS bad? |