Re: BUG #8269: the recovery_target_inclusive is always considered as false - Mailing list pgsql-bugs

From Fujii Masao
Subject Re: BUG #8269: the recovery_target_inclusive is always considered as false
Date
Msg-id CAHGQGwFqwgniFG15hGmb1=5XSgkpimfSq2qFG4Cb5XGfSpcEvw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #8269: the recovery_target_inclusive is always considered as false  (Eyal Kaspi <eyal.kaspi@delphix.com>)
List pgsql-bugs
On Tue, Jul 2, 2013 at 3:05 AM, Eyal Kaspi <eyal.kaspi@delphix.com> wrote:
> You are right. I did not read the doc correctly.
>
> Is there anyway to specify a timestamp and get the database to recover to
> the first transaction after that point?

Currently there is no easy way to do that. Basically you need to find out
the XID or the time of that first transaction, e.g., by using pg_xlogdump,
and specify it in the recovery target.

Regards,

--
Fujii Masao

pgsql-bugs by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled
Next
From: Tom Lane
Date:
Subject: Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled