Re: odd output in restore mode

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Subject: Re: odd output in restore mode
Date: 2008-05-13 01:06:26
Message-ID: 200805122106.27351.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-05-13 01:15:55 Re: odd output in restore mode
Previous Message Simon Riggs 2008-05-12 23:37:53 Re: odd output in restore mode

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2008-05-13 01:15:55 Re: odd output in restore mode
Previous Message Tom Lane 2008-05-13 00:19:33 Re: Partial match in GIN (next vesrion)