X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B53329FB2DB for ; Thu, 13 Jul 2006 21:40:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 91383-08 for ; Thu, 13 Jul 2006 21:40:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2FFFE9FB2A9 for ; Thu, 13 Jul 2006 21:40:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6E0eAnI023855; Thu, 13 Jul 2006 20:40:11 -0400 (EDT) To: FM cc: Mailing List Postgres-Admin Subject: Re: corruption since 7.4.13 update ? In-reply-to: <44AC1EAE.9030305@lexum.umontreal.ca> References: <44AC1EAE.9030305@lexum.umontreal.ca> Comments: In-reply-to FM message dated "Wed, 05 Jul 2006 16:18:54 -0400" Date: Thu, 13 Jul 2006 20:40:10 -0400 Message-ID: <23854.1152837610@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/104 X-Sequence-Number: 22350 FM writes: > I'e got a very strange (scary) problem. > ERROR: could not read block 81235 of relation "pg_largeobject": > Input/output error This one is very strongly indicative of a disk hardware problem. The others look like they could be consequences of catalog corruption ensuing from a flaky disk. If I were you I'd run some hardware diagnostics. Also see if you can pg_dump ... regards, tom lane