Message-ID: <4828FFA6.7000806@dunslane.net>
Date: Mon, 12 May 2008 22:40:38 -0400
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text
	SeaMonkey/1.0.9
MIME-Version: 1.0
To: Robert Treat <xzilla@users.sourceforge.net>
CC: pgsql-hackers@postgresql.org, Simon Riggs <simon@2ndquadrant.com>
Subject: Re: odd output in restore mode
References: <4828AF1D.7060405@dunslane.net>
	<1210630440.29684.249.camel@ebony.site>
	<4828CB9D.7070102@dunslane.net>
	<200805122106.27351.xzilla@users.sourceforge.net>
In-Reply-To: <200805122106.27351.xzilla@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


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.

cheers

andrew