Subject: Re: odd output in restore mode
From: Simon Riggs <simon@2ndquadrant.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Robert Treat <xzilla@users.sourceforge.net>, pgsql-hackers@postgresql.org
In-Reply-To: <4828FFA6.7000806@dunslane.net>
References: <4828AF1D.7060405@dunslane.net>
	<1210630440.29684.249.camel@ebony.site> <4828CB9D.7070102@dunslane.net>
	<200805122106.27351.xzilla@users.sourceforge.net>
	<4828FFA6.7000806@dunslane.net>
Content-Type: text/plain
Date: Tue, 13 May 2008 06:37:24 +0100
Message-Id: <1210657044.29684.271.camel@ebony.site>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Mon, 2008-05-12 at 22:40 -0400, Andrew Dunstan wrote:
> 
> Robert Treat wrote:
> > On Monday 12 May 2008 18:58:37 Andrew Dunstan wrote:
> >   
> >> Simon Riggs wrote:
> >>     
> >>>> Lastly, not quite related to this output, but in the same general area,
> >>>> should we have an option on pg_standby to allow removing the archive
> >>>> file after it has been restored?
> >>>>         
> >>> There already is one, but its more complex than that. (%r)
> >>>       
> >> I was using %r. But the WAL files that have been restored (according to
> >> the log) are still in the archive dir. So it looks like %r isn't working
> >> properly.
> >>

> > Are you sure you've moved passed the latest restart point? Just because a WAL 
> > file has been processed doesn't mean it can be deleted. 
> >
> Thanks. It wasn't that, but when I ran with the very latest patches this 
> problem went away.
> 

Thanks for testing.

-- 
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com