X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 3108D11F6B7C for ; Tue, 18 Apr 2006 17:35:03 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.559 X-Spam-Level: X-Spam-Status: No, score=-2.559 required=5 tests=[AWL=0.040, BAYES_00=-2.599] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id xqBZ0l972d6N for ; Tue, 18 Apr 2006 17:34:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from chilco.textdrive.com (chilco.textdrive.com [207.7.108.242]) by postgresql.org (Postfix) with ESMTP id E18DA11F6B6A for ; Tue, 18 Apr 2006 17:34:56 -0300 (ADT) Received: from [192.168.1.109] (unknown [209.149.57.250]) by chilco.textdrive.com (Postfix) with ESMTP id 16535DBB91; Tue, 18 Apr 2006 20:36:10 +0000 (UTC) In-Reply-To: <18515.1145390275@sss.pgh.pa.us> References: <17920.1145387726@sss.pgh.pa.us> <18515.1145390275@sss.pgh.pa.us> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8BF49FC5-C860-4F2B-BCDE-FDEDFA06D96D@sitening.com> Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit From: "Thomas F. O'Connell" Subject: Re: Invalid Page Headers Date: Tue, 18 Apr 2006 15:34:53 -0500 To: Tom Lane X-Mailer: Apple Mail (2.749.3) X-Archive-Number: 200604/172 X-Sequence-Number: 21341 On Apr 18, 2006, at 2:57 PM, Tom Lane wrote: > "Thomas F. O'Connell" 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)