Re: Invalid Page Header

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: "Christopher A(dot) Goodfellow" <cgoodfellow(at)tealuxe(dot)com>
Cc: "'Pgsql-Novice (E-mail)'" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Invalid Page Header
Date: 2006-03-09 19:16:46
Message-ID: 20060309191646.GA91374@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Thu, Mar 09, 2006 at 01:48:40PM -0500, Christopher A. Goodfellow wrote:
> I have read quite a bit in the archives and it seems the best way is to
> zero_damaged_pages. I did a search for zero_damaged_pages. Is it as simple
> as adding zero_damaged_pages to postgresql.conf and restarting the
> postmaster?

To be honest, I'd forgotten about zero_damaged_pages (and I must
have overlooked the recent messages in -hackers that mention it).
I'd prefer to set it in a particular session rather than in
postgresql.conf so it happened only when and where I want. Here's
an example:

test=# select count(*) from foo;
ERROR: invalid page header in block 10 of relation "foo"
test=# set zero_damaged_pages to on;
SET
test=# select count(*) from foo;
WARNING: invalid page header in block 10 of relation "foo"; zeroing out page
WARNING: invalid page header in block 20 of relation "foo"; zeroing out page
WARNING: invalid page header in block 30 of relation "foo"; zeroing out page
count
-------
9445
(1 row)

test=# set zero_damaged_pages to off;
SET

--
Michael Fuhr

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2006-03-09 19:20:04 Re: Invalid Page Header
Previous Message Kevin Crenshaw 2006-03-09 19:13:13 Re: Storing sensitive data