pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: does wal archiving block the current client connection?
Date: Fri, 19 May 2006 12:17:29 -0400
Message-ID: <1879.1148055449@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.64.0605190901140.7012@discord.home.frostconsultingllc.com>
References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org>
	<Pine.LNX.4.64.0605161119330.3380@glacier.frostconsultingllc.com>
	<15699.1147840569@sss.pgh.pa.us>
	<1147858398.2646.150.camel@localhost.localdomain>
	<19436.1147874478@sss.pgh.pa.us>
	<Pine.LNX.4.64.0605170909020.3380@glacier.frostconsultingllc.com>
	<7583.1147922685@sss.pgh.pa.us>
	<Pine.LNX.4.64.0605172134370.7012@discord.home.frostconsultingllc.com>
	<8269.1147927511@sss.pgh.pa.us>

Jeff Frost <jeff@frostconsultingllc.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



view thread (55+ messages)  latest in thread

Message-ID: <1879.1148055449@sss.pgh.pa.us>
Permalink:  ../1879.1148055449@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1879.1148055449@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jeff@frostconsultingllc.com, simon@2ndquadrant.com, pgsql-hackers@postgresql.org
  Subject: Re: does wal archiving block the current client connection?
  In-Reply-To: <1879.1148055449@sss.pgh.pa.us>
  References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org> <Pine.LNX.4.64.0605161119330.3380@glacier.frostconsultingllc.com> <15699.1147840569@sss.pgh.pa.us> <1147858398.2646.150.camel@localhost.localdomain> <19436.1147874478@sss.pgh.pa.us> <Pine.LNX.4.64.0605170909020.3380@glacier.frostconsultingllc.com> <7583.1147922685@sss.pgh.pa.us> <Pine.LNX.4.64.0605172134370.7012@discord.home.frostconsultingllc.com> <8269.1147927511@sss.pgh.pa.us> <1879.1148055449@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox