Jeff Frost <jeff(at)frostconsultingllc(dot)com> writes:
> So, that, immediately begs the question as to why the docs indicate we
> should clear out all the files in the pg_xlog directory before
> beginning the restore? Wouldn't it be better to keep them in place?
IIRC, the docs recommend getting rid of any xlog files that were copied
as part of your base backup: they are either too old to be interesting
(if finished before the base backup started) or not to be trusted
because they might be incomplete (if they were actively being written
while the base backup proceeded). You have to get this range of data
from your archive in order to trust it.
The reason we avoid overwriting data automatically is that we don't know
what is in your local pg_xlog exactly; there might be xlog files that
are newer than the base backup and potentially contain data not
available anywhere else (if for some reason they never got copied to the
archive area). So prudence dictates not wiping them out.
> Ohhhh...I guess I misunderstood the meaning of base backup. So, what I really
> need if my .backup file is named: 000000010000000500000051.00FB6C60.backup,
> then I need at least the following to do a restore:
> PGDATA base backup
> and then any archived wal files that come after 51?
You got it.
regards, tom lane
In response to
pgsql-admin by date
|Next:||From: David Bear||Date: 2005-06-23 19:27:44|
|Subject: psql copy errors|
|Previous:||From: Jeff Frost||Date: 2005-06-23 18:41:17|
|Subject: Re: restoring wal archive and pg_xlog dir |