pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas F. O'Connell <tfo@sitening.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Invalid Page Headers
Date: Tue, 18 Apr 2006 15:34:53 -0500
Message-ID: <8BF49FC5-C860-4F2B-BCDE-FDEDFA06D96D@sitening.com> (raw)
In-Reply-To: <18515.1145390275@sss.pgh.pa.us>
References: <B8F30540-C0A5-4CF7-8DB2-867DFF25E58D@sitening.com>
	<A8661BBC-FC31-4AA1-BA22-6FAC15B32D74@sitening.com>
	<17920.1145387726@sss.pgh.pa.us>
	<C2B4E2FA-1C42-4C21-97DF-3CB6D3CAB4BF@sitening.com>
	<18515.1145390275@sss.pgh.pa.us>


On Apr 18, 2006, at 2:57 PM, Tom Lane wrote:

> "Thomas F. O'Connell" <tfo@sitening.com> writes:
>> In the meantime, should I leave the database online while I attempt
>> to recover? It's still unclear to me whether postgres will restart
>> with invalid page headers. I certainly can't run pg_dumpall, for
>> instance.
>
> Has the database successfully checkpointed since the last error
> occurrence?  If so, I wouldn't foresee any problem with a shutdown.
> If checkpoints are failing then you probably won't be able to shut
> down without getting the same error.  (Use pg_controldata if you're
> not sure about when the last checkpoint happened.)

The last checkpoint was at Tue Apr 18 15:30:24 2006, so it looks like  
we're fine on that front.

>> I'm glad that there have so far been only 3 relations affected... :(
>
> You mean, three that you know about :-(

True enough. The RAID is rebuilding with new drives right now. Then  
we'll recover the relations known to be corrupt.

(If a pg_toast relation had an invalid page header, would restoring  
the table to which it's connected solve the problem?)

Then I'll do a pg_dumpall. If that works, that should be a pretty  
good indicator that the database is in a stable state, right?

--
Thomas F. O'Connell
Database Architecture and Programming
Sitening, LLC

http://www.sitening.com/
3004 B Poston Avenue
Nashville, TN 37203-1314
615-260-0005 (cell)
615-469-5150 (office)
615-469-5151 (fax)



view thread (10+ messages)  latest in thread

Message-ID: <8BF49FC5-C860-4F2B-BCDE-FDEDFA06D96D@sitening.com>
Permalink:  ../8BF49FC5-C860-4F2B-BCDE-FDEDFA06D96D@sitening.com/
Also on:    postgresql.org/message-id/8BF49FC5-C860-4F2B-BCDE-FDEDFA06D96D@sitening.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tfo@sitening.com, tgl@sss.pgh.pa.us
  Subject: Re: Invalid Page Headers
  In-Reply-To: <8BF49FC5-C860-4F2B-BCDE-FDEDFA06D96D@sitening.com>
  References: <B8F30540-C0A5-4CF7-8DB2-867DFF25E58D@sitening.com> <A8661BBC-FC31-4AA1-BA22-6FAC15B32D74@sitening.com> <17920.1145387726@sss.pgh.pa.us> <C2B4E2FA-1C42-4C21-97DF-3CB6D3CAB4BF@sitening.com> <18515.1145390275@sss.pgh.pa.us> <8BF49FC5-C860-4F2B-BCDE-FDEDFA06D96D@sitening.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox