Re: BUG #8269: the recovery_target_inclusive is always considered as false

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Eyal Kaspi <eyal(dot)kaspi(at)delphix(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8269: the recovery_target_inclusive is always considered as false
Date: 2013-07-01 22:43:02
Message-ID: CAHGQGwFqwgniFG15hGmb1=5XSgkpimfSq2qFG4Cb5XGfSpcEvw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jul 2, 2013 at 3:05 AM, Eyal Kaspi <eyal(dot)kaspi(at)delphix(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-07-01 23:27:26 Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled
Previous Message Andrew Dunstan 2013-07-01 21:51:28 Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled