pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Subbiah, Stalin <SSubbiah@netopia.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Archive WAL Logs Failed
Date: Wed, 22 Nov 2006 22:31:00 -0500 (EST)
Message-ID: <200611230331.kAN3V0T07467@momjian.us> (raw)
In-Reply-To: <1163842859.27956.737.camel@silverbirch.site>


Added to 8.1.5 release notes:

	<listitem><para>Fix rare bug in continuous archiving
	(Tom)</para></listitem>


---------------------------------------------------------------------------

 Simon Riggs wrote:
> On Tue, 2006-11-07 at 10:15 -0800, Subbiah, Stalin wrote:
> 
> > Yesterday, we'd archiver problems in copying archived wal files from
> > pg_xlog to archive destination at the end of full hotbackup. Below are
> > the errors from server logs.
> > 
> > What makes me to wonder is that why does archiver tries to copy
> > "000000010000000800000074.0066C9C0.backup" again when it's already
> > been archived. As soon I removed
> > "000000010000000800000074.0066C9C0.backup" from archive location, then
> > archiver was happy to copy again and moved on to archiving
> > 000000010000000800000074 etc.
> > 
> > 2006-11-07 00:35:23 CST  LOG:  archived transaction log file
> > "000000010000000800000074.0066C9C0.backup" 
> > 2006-11-07 00:35:23 CST  LOG:  archive command "test !
> > -f /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup &&
> > cp
> > pg_xlog/000000010000000800000074.0066C9C0.backup /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup" failed: return code 256
> > 
> > Any idea what may be going on here.
> 
> > PG814, RH4.0
> 
> This was a bug fixed in 8.1.5
> 
> http://archives.postgresql.org/pgsql-committers/2006-06/msg00305.php
> 
> I notice it isn't mentioned in the 8.1.5 release notes. You should
> upgrade.
> 
> -- 
>   Simon Riggs             
>   EnterpriseDB   http://www.enterprisedb.com
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org

-- 
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



view thread (5+ messages)

Message-ID: <200611230331.kAN3V0T07467@momjian.us>
Permalink:  ../200611230331.kAN3V0T07467@momjian.us/
Also on:    postgresql.org/message-id/200611230331.kAN3V0T07467@momjian.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: bruce@momjian.us, simon@2ndquadrant.com, SSubbiah@netopia.com
  Subject: Re: Archive WAL Logs Failed
  In-Reply-To: <200611230331.kAN3V0T07467@momjian.us>
  References: <1163842859.27956.737.camel@silverbirch.site> <200611230331.kAN3V0T07467@momjian.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