Skip site navigation (1) Skip section navigation (2)

Re: does wal archiving block the current client connection?

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 (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-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

In response to

pgsql-hackers by date

Next:From: Jeff FrostDate: 2006-05-19 16:36:47
Subject: Re: does wal archiving block the current client connection?
Previous:From: Joshua D. DrakeDate: 2006-05-19 16:32:17
Subject: Re: [OT] MySQL is bad, but THIS bad?

pgsql-admin by date

Next:From: Jeff FrostDate: 2006-05-19 16:36:47
Subject: Re: does wal archiving block the current client connection?
Previous:From: Simon RiggsDate: 2006-05-19 16:27:33
Subject: Re: [ADMIN] does wal archiving block the current client connection?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group