Re: help troubleshooting invalid page header error

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Cory Zue <czue(at)dimagi(dot)com>, chiru r <chirupg(at)gmail(dot)com>
Cc: Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>, PostgreSQL General Discussion Forum <pgsql-general(at)postgresql(dot)org>
Subject: Re: help troubleshooting invalid page header error
Date: 2014-12-29 15:00:11
Message-ID: 363814273.1369637.1419865211866.JavaMail.yahoo@jws100132.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Cory Zue <czue(at)dimagi(dot)com> wrote:

> I was able to get the database back to a normal functional state
> using the zero_damaged_pages flag. However, after getting
> everything working and starting to use the database again, I am
> again getting "invalid page header" errors on a certain table.
>
> Does this imply there is a hardware issue on my machine? Is there
> anything else that could be causing this to come back?

In my personal experience bad hardware is the most common cause,
followed by buggy device drivers (where an OS software upgrade
prevented further corruption), followed by using incorrect
procedures for backup, restore, replication setup, or node
promotion. For example, not excluding files under pg_xlog from a
base backup or deleting (or moving) the backup_label file can cause
corruption.

For a more complete discussion, see this blog page:

http://rhaas.blogspot.com/2012/03/why-is-my-database-corrupted.html

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ronald Peterson 2014-12-29 15:06:41 extra function calls from query returning composite type
Previous Message sramay 2014-12-29 12:42:18 vacuum vs pg_repack vs pg_reorg