From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
---|---|
To: | Romain Thouvenin <rthouvenin(at)sfwan(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: problem with WAL files |
Date: | 2005-06-30 17:06:24 |
Message-ID: | Pine.LNX.4.63.0506301003050.15741@discord.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Romain,
This is a problem I ran into during testing as well. It seems that your base
backup must also include the in use wal file. IN your case:
00000001000000000000000B. So, I think the restore documentation is slightly
misleading. In my experience, what you really need to do is remove all wal
files from your pg_xlog directory, then put in the in use wal file from when
you did your base backup (00000001000000000000000B in your case), put in the
recovery.conf and then start postgresql. This procedure works well for me,
but I didn't quite grasp that initially when reading the documentation on how
to backup/restore with PITR.
On Thu, 30 Jun 2005, Romain Thouvenin wrote:
> But when I put the recovery.conf file and try to start postgres, it fails.
> The log file says :
>
> 2005-06-30 17:57:50 LOG: could not open file "C:/Program
> Files/PostgreSQL/8.0/data/pg_xlog/00000001000000000000000B" (log file 0,
> segment 11): No such file or directory
--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
From | Date | Subject | |
---|---|---|---|
Next Message | Uwe C. Schroeder | 2005-06-30 17:17:01 | Re: Linux syslog question ... |
Previous Message | Romain Thouvenin | 2005-06-30 16:49:48 | problem with WAL files |