From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: odd output in restore mode |
Date: | 2008-05-13 05:37:24 |
Message-ID: | 1210657044.29684.271.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-05-13 05:44:35 | Re: odd output in restore mode |
Previous Message | Josh Tolley | 2008-05-13 05:23:17 | Problem returning strings with pgsql 8.3.x |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-05-13 05:44:35 | Re: odd output in restore mode |
Previous Message | Andrew Dunstan | 2008-05-13 03:03:25 | Re: odd output in restore mode |