On Wed, Oct 26, 2011 at 12:16 PM, Florian Pflug <fgp(at)phlo(dot)org> wrote:
>> Chris' clog error was caused by a file read error. The file was
>> opened, we did a seek within the file and then the call to read()
>> failed to return a complete page from the file.
>> The xid shown is 22811359, which is the nextxid in the control file.
>> So StartupClog() must have failed trying to read the clog page from disk.
>> That isn't a Hot Standby problem, a recovery problem nor is it certain
>> its a PostgreSQL problem.
> It's very likely that it's a PostgreSQL problem, though. It's probably
> not a pilot error since it happens even for backups taken with pg_basebackup(),
> so the only explanation other than a PostgreSQL bug is broken hardware or
> a pretty serious kernel/filesystem bug.
The way forwards here is for someone to show the clog file that causes
the error and find out why the call to read() fails.
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
In response to
pgsql-hackers by date
|Next:||From: Aidan Van Dyk||Date: 2011-10-26 11:54:16|
|Subject: Re: Hot Backup with rsync fails at pg_clog if under load|
|Previous:||From: MauMau||Date: 2011-10-26 11:31:19|
|Subject: Re: patch for distinguishing PG instances in event log v2|