| 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:32:42 |
| Message-ID: | Pine.LNX.4.64.0605190931180.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:
> 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?
I looked through /var/log/messages* and there wasn't a restart prior to the
problem in the logs. They go back to April 16. The postmaster was restarted
on May 15th (this Monday), but that was after the reported 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 | Jeff Frost | 2006-05-19 16:36:47 | Re: does wal archiving block the current client connection? |
| Previous Message | Simon Riggs | 2006-05-19 16:27:33 | Re: [ADMIN] does wal archiving block the current client connection? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Frost | 2006-05-19 16:36:47 | Re: does wal archiving block the current client connection? |
| Previous Message | Joshua D. Drake | 2006-05-19 16:32:17 | Re: [OT] MySQL is bad, but THIS bad? |