| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: odd output in restore mode |
| Date: | 2008-05-13 02:40:38 |
| Message-ID: | 4828FFA6.7000806@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-05-13 02:41:11 | Re: Syntax decisions for pl/pgsql RAISE extension |
| Previous Message | Tom Lane | 2008-05-13 01:38:58 | Re: odd output in restore mode |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-05-13 03:03:25 | Re: odd output in restore mode |
| Previous Message | Tom Lane | 2008-05-13 01:38:58 | Re: odd output in restore mode |