From: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
---|---|
To: | dx k9 <bitsandbytes88(at)hotmail(dot)com> |
Cc: | posgres support <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: recovery.conf |
Date: | 2009-10-29 23:57:22 |
Message-ID: | d3ab2ec80910291657n6f0b0fb5u93b3ea22d8e50641@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Oct 29, 2009 at 5:13 PM, dx k9 <bitsandbytes88(at)hotmail(dot)com> wrote:
> Hi all -
>
> I'm trying to do a PITR and I've noticed that every time I try it, it ups
> the number it's looking for by one.
>
What's in your recovery.conf?
>
> 00000001.history
> 00000002.history
> .
> .
> 00000008.history
>
> For example one of my transaction log files name is
> 0000000100000218000000C1
>
> Instead of looking for 0000000100000218000000C1, it replaces the first 1,
> with a 2 or
> 0000000200000218000000C1, I'm all the way up to 8 now. How do I tell it to
> look for 1 or
> 0000000100000218000000C1 again.
>
>
Every time your database opens, it comes onto a new timeline. I don't
*believe* you can go back to an older timeline once you've opened the
database for operation.
--Scott
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Mead | 2009-10-30 00:00:27 | Re: recovery.conf |
Previous Message | dx k9 | 2009-10-29 21:13:26 | recovery.conf |