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
Subject: Re: does wal archiving block the current client connection?
Date: Fri, 19 May 2006 11:49:18 -0400
Message-ID: <578.1148053758@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.64.0605190818350.5387@discord.home.frostconsultingllc.com>
References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org>
	<1147728181.5074.73.camel@localhost.localdomain>
	<Pine.LNX.4.64.0605151424500.9581@discord.dyndns.org>
	<1147733193.5074.87.camel@localhost.localdomain>
	<Pine.LNX.4.64.0605151554000.9581@discord.dyndns.org>
	<1147781287.2646.32.camel@localhost.localdomain>
	<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>
	<Pine.LNX.4.64.0605172243190.7012@discord.home.frostconsultingllc.com>
	<1147942877.2646.388.camel@localhost.localdomain>
	<Pine.LNX.4.64.0605180750580.5387@discord.home.frostconsultingllc.com>
	<Pine.LNX.4.64.0605180955570.14711@glacier.frostconsultingllc.com>
	<1148041593.2646.592.camel! @localhost.loca{ h@ | <Pine.LNX.4.64.0605190818350.5387@discord.home.frostconsultingllc.com>

Jeff Frost <jeff@frostconsultingllc.com> writes:
> Do you think the postmaster on 5432 is trying to archive the other 
> postmaster's WAL files somehow?

Not as long as they aren't in the same data directory ;-).  What Simon
was wondering about was whether an archiver process had somehow been
left over from a previous incarnation of the test postmaster.  The thing
to do is look through "ps auxww" (or local equivalent) and see if you
see more than one thing calling itself an archiver process.

(Whether or not this explains Jeff's problem, it definitely seems like
a failure mode that we need to guard against.  We go to great lengths
to prevent a new postmaster from starting when there are still live
backends from a previous postmaster, but I don't think that interlock
is effective for the archiver.)

			regards, tom lane



view thread (55+ messages)  latest in thread

Message-ID: <578.1148053758@sss.pgh.pa.us>
Permalink:  ../578.1148053758@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/578.1148053758@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
  Subject: Re: does wal archiving block the current client connection?
  In-Reply-To: <578.1148053758@sss.pgh.pa.us>
  References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org> <1147728181.5074.73.camel@localhost.localdomain> <Pine.LNX.4.64.0605151424500.9581@discord.dyndns.org> <1147733193.5074.87.camel@localhost.localdomain> <Pine.LNX.4.64.0605151554000.9581@discord.dyndns.org> <1147781287.2646.32.camel@localhost.localdomain> <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> <Pine.LNX.4.64.0605172243190.7012@discord.home.frostconsultingllc.com> <1147942877.2646.388.camel@localhost.localdomain> <Pine.LNX.4.64.0605180750580.5387@discord.home.frostconsultingllc.com> <Pine.LNX.4.64.0605180955570.14711@glacier.frostconsultingllc.com> <578.1148053758@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