pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: does wal archiving block the current client connection?
Date: Fri, 19 May 2006 16:56:49 +0100
Message-ID: <1148054209.2646.659.camel@localhost.localdomain> (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.localdomain>
	<Pine.LNX.4.64.0605190818350.5387@discord.home.frostconsultingllc.com>

On Fri, 2006-05-19 at 08:23 -0700, Jeff Frost wrote:
> On Fri, 19 May 2006, Simon Riggs wrote:
> 
> > On Thu, 2006-05-18 at 10:08 -0700, Jeff Frost wrote:
> >
> >> May 18 08:00:18 discord postgres[20228]: [129-1] LOG:  archived transaction log file "00000001000000000000007F"
> >> May 18 08:00:41 discord postgres[20573]: [254-1] LOG:  archived transaction log file "00000001000000000000007F"
> >> May 18 08:00:41 discord postgres[20573]: [255-1] WARNING:  could not rename file "pg_xlog/archive_status/00000001000000000000007F.ready" to
> >> May 18 08:00:41 discord postgres[20573]: [255-2]  "pg_xlog/archive_status/00000001000000000000007F.done": No such file or directory
> >
> > I'm not clear how you can have two processes both issuing this message,
> > since it is only the archiver process that ever says this.
> >
> > Do you have two archivers running on this system?
> > pid = 20229 and pid = 20573
> >
> > Presumably pg_xlog/archive_status/00000001000000000000007F.done already
> > exists?
> >
> > Are there two postmasters running (at all)?
> > Is there somehow an archiver process running from a previously shutdown
> > postmaster (somehow)?
> 
> Ah!!  Good catch Simon!  There are in fact two postmasters running on this 
> system.  The normal postmaster running in /var/lib/pgsql on port 5432 and this 
> test postmaster running on port 55432.  The 8.0.7 postmaster on port 5432 
> shows the following for it's archive_command though:
> 
> template1=# show archive_command;
>   archive_command
> -----------------
>   unset
> (1 row)
> 
> and the port 55432 postmaster shows:
> 
> template1=# show archive_command;
>                     archive_command
> ------------------------------------------------------
>   /usr/local/pgsql-8.1.3/bin/archive_test.sh "%p" "%f"
> (1 row)
> 
> Do you think the postmaster on 5432 is trying to archive the other 
> postmaster's WAL files somehow?

Some wierd interaction is occurring. The log showed two attempts to
archive the file, the second one each time failing, as you'd expect. But
two archivers should not be accessing the same data directory.

What were those two pids? Which postmasters are they children of?

Give me some more info and I can probably track down a bug...

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com




view thread (55+ messages)  latest in thread

Message-ID: <1148054209.2646.659.camel@localhost.localdomain>
Permalink:  ../1148054209.2646.659.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1148054209.2646.659.camel@localhost.localdomain

 · 

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: simon@2ndquadrant.com, jeff@frostconsultingllc.com, tgl@sss.pgh.pa.us
  Subject: Re: does wal archiving block the current client connection?
  In-Reply-To: <1148054209.2646.659.camel@localhost.localdomain>
  References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org> <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.localdomain> <Pine.LNX.4.64.0605190818350.5387@discord.home.frostconsultingllc.com> <1148054209.2646.659.camel@localhost.localdomain>

* 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