From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)mail(dot)com> |
Cc: | wd <wd(at)wdicc(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Restore postgres to specific time |
Date: | 2012-11-27 17:40:33 |
Message-ID: | CAMkU=1y9p4Ns8eWAKmHKT21Gchq_T_kTNeMfEQsNV1EUHGsr=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Nov 27, 2012 at 6:59 AM, Kevin Grittner <kgrittn(at)mail(dot)com> wrote:
> wd wrote:
>
>> the time is between backup start and stop.
>
> That is the problem -- until the point where pg_stop_backup() was
> run PostgreSQL can't be sure of having a consistent database. It is
> waiting from enough WAL to get it there. My practice is always to
> keep the last two base backups and all WAL from the start of the
> earlier one to current. If I want to recover to a point in time
> which was during a backup, I use the previous base backup, which is
> complete and usable.
>
> It does seem that there is an opportunity here to make it more
> clear what is happening.
It seems like the code is already there to throw an error, it is just
that hot_standby=on somehow suppresses it during this window.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Flower | 2012-11-27 20:21:02 | Re: Correlation in pg_stats |
Previous Message | Merlin Moncure | 2012-11-27 16:48:21 | Re: create table in memory |