Re: [GENERAL] WAL ends before end time of backup dump

2006-11-08 Thread Jeff Davis
On Wed, 2006-11-08 at 09:39 -0500, Woody Woodring wrote: > Which Sunday? Could you have been bitten by some DST time shift? There > were 2 1ams a couple of weeks ago. > Hah, interesting idea, but it wasn't that the basebackup didn't exist, and it wasn't that I had two of them close together. I

Re: [GENERAL] WAL ends before end time of backup dump

2006-11-08 Thread Woody Woodring
-general@postgresql.org Subject: Re: [GENERAL] WAL ends before end time of backup dump On Tue, 2006-11-07 at 17:20 -0500, Tom Lane wrote: > Jeff Davis <[EMAIL PROTECTED]> writes: > > LOG: restored log file "00010017002B" from archive > > LOG: record

Re: [GENERAL] WAL ends before end time of backup dump

2006-11-07 Thread Jeff Davis
On Tue, 2006-11-07 at 17:20 -0500, Tom Lane wrote: > Jeff Davis <[EMAIL PROTECTED]> writes: > > LOG: restored log file "00010017002B" from archive > > LOG: record with zero length at 17/2B6EACC8 > > LOG: redo done at 17/2B6EAC84 > > It looks to me like you archived this log file bef

Re: [GENERAL] WAL ends before end time of backup dump

2006-11-07 Thread Jeff Davis
On Tue, 2006-11-07 at 11:15 -0800, Jeff Davis wrote: > Version: 8.1.4 > [ snip ] > OG: restored log file "00010017002B" from archive > LOG: record with zero length at 17/2B6EACC8 > LOG: redo done at 17/2B6EAC84 > LOG: restored log file "00010017002B" from archive > LO

Re: [GENERAL] WAL ends before end time of backup dump

2006-11-07 Thread Tom Lane
Jeff Davis <[EMAIL PROTECTED]> writes: > LOG: restored log file "00010017002B" from archive > LOG: record with zero length at 17/2B6EACC8 > LOG: redo done at 17/2B6EAC84 It looks to me like you archived this log file before it was fully written. You should take a close look at your

[GENERAL] WAL ends before end time of backup dump

2006-11-07 Thread Jeff Davis
Version: 8.1.4 I am having a problem restoring one of my base backups. I took a successful backup of the production DB already since this one, and this is just a routine test, so it's fortunately not an emergency. I think that I either have a corrupted base backup or corrupted WAL segments, or ma