From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Woody Woodring <george(dot)woodring(at)iglass(dot)net> |
Cc: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: WAL ends before end time of backup dump |
Date: | 2006-11-08 17:17:01 |
Message-ID: | 1163006221.31124.449.camel@dogma.v10.wvs |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 had one base
backup, and apparently one of the logs archived at that time is corrupt
(or perhaps archived too soon).
The log file has bytes throughout, but I suppose that doesn't tell me
anything because of the recycling.
It would be handy if there was a way to check whether archived log files
are good or not without trying to go through recovery.
I still really don't know what caused this. I think it may have
something to do with a lot of activity happening during my base backup.
I am sending syslog data to the database, and I imagine a lot of syslog
data is generated by other cron scripts at that time.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Ed L. | 2006-11-08 17:18:02 | 8.1.2 postmaster died |
Previous Message | Worky Workerson | 2006-11-08 16:35:39 | "Broken" Plan? Nested Loop IN Join vs. Nested Loop/Hash Aggregate |