From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
Cc: | "wd" <wd(at)wdicc(dot)com>, "Jeff Janes" <jeff(dot)janes(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Restore postgres to specific time |
Date: | 2012-11-27 15:06:14 |
Message-ID: | 8575.1354028774@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Kevin Grittner" <kgrittn(at)mail(dot)com> writes:
> 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.
Seems like we could throw an error if the requested stop time is earlier
than the pg_stop_backup time. (That should then allow some code
simplification --- I imagine currently we're doing a max() calculation
somewhere ...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2012-11-27 15:29:14 | Re: create table in memory |
Previous Message | Kevin Grittner | 2012-11-27 14:59:39 | Re: Restore postgres to specific time |