Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5FIe2a03202 for ; Fri, 15 Jun 2001 14:40:02 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f5FIcu325357; Fri, 15 Jun 2001 14:38:56 -0400 (EDT) To: brian cc: "pgsql-admin@postgresql.org" Subject: Re: vacuum error In-reply-to: <3B2A39B5.5A217325@misanthropia.com> References: <3B2A39B5.5A217325@misanthropia.com> Comments: In-reply-to brian message dated "Fri, 15 Jun 2001 09:37:09 -0700" Date: Fri, 15 Jun 2001 14:38:56 -0400 Message-ID: <25354.992630336@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/94 X-Sequence-Number: 1651 brian writes: > I have a small database with a few tables and a view. When I issue the > vacuum command, I get: > ERROR: cannot read block 5 of pg_description_objoid_index: Input/output > error Ugh, sounds like a disk hardware problem :-(. Better think about new drives, or at least reformatting the one you have. As a short-term workaround to be able to dump your DB, I'd suggest just DROP INDEX pg_description_objoid_index; (you'll have to set the magic switch that allows modification of system tables first). You could try reindexing pg_description, but since this is a highly noncritical index, it's probably easier just to get rid of it. regards, tom lane