On Tue, 2006-11-07 at 11:15 -0800, Jeff Davis wrote: > Version: 8.1.4 > [ snip ] > OG: restored log file "00000001000000170000002B" from archive > LOG: record with zero length at 17/2B6EACC8 > LOG: redo done at 17/2B6EAC84 > LOG: restored log file "00000001000000170000002B" from archive > LOG: archive recovery complete > LOG: database system is ready > LOG: transaction ID wrap limit is 1094453440, limited by database > "postgres" > >From the 8.1.4 source I see that: /* * Currently, xl_len == 0 must be bad data, but that might not be true Does that mean that I must have a corrupt WAL segment file 00000001000000170000002B? Is it possible this was caused by a bug? Would an already known bug possibly cause this problem? I am sending the transaction logs to an NFS mount. I consider it to be reliable storage, so I can't see how that would have been corrupted unless it was sent that way by PostgreSQL. Regards, Jeff Davis
