xlog corruption

From: Jameison Martin <jameisonb(at)yahoo(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: xlog corruption
Date: 2012-02-28 00:30:56
Message-ID: 1330389056.92402.YahooMailNeo@web39403.mail.mud.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'd like to get some clarification around an architectural point about recovery. I see that it is normal to see "unexpected pageaddr" errors during recovery because of the way Postgres overwrites old log files, and thus this is taken to be a normal termination condition, i.e. the end of the log (see http://doxygen.postgresql.org/xlog_8c.html#a0519e464bfaa79bde3e241e6cff986c7). My question is how does recovery distinguish between the actual end of the log as opposed to a log file corruption (e.g. torn page)?  

I'd like to be able to distinguish between a corruption in the log vs. a normal recovery condition if possible.

Thanks.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jameison Martin 2012-02-28 00:36:26 synchronous replication: blocking commit on the master
Previous Message Tom Lane 2012-02-27 23:41:40 Re: pg_class.relnamespace NOT IN pg_namespace.oid