Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 9D50D9FB1BA; Fri, 5 Jan 2007 18:22:17 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 67223-03; Fri, 5 Jan 2007 18:21:34 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id BE5829FA6B3; Fri, 5 Jan 2007 18:21:37 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Fri, 5 Jan 2007 22:21:34 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 05 Jan 2007 16:21:34 -0600 Subject: Re: vacuum fails with 'invalid page header' message From: Scott Marlowe To: Geoffrey Cc: pgsql-admin@postgresql.org, pgsql general In-Reply-To: <459ECEE8.5030806@3times25.net> References: <459EC34E.3070304@3times25.net> <459ECEE8.5030806@3times25.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1168035694.3421.52.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 05 Jan 2007 16:21:34 -0600 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/49 X-Sequence-Number: 24205 On Fri, 2007-01-05 at 16:19, Geoffrey wrote: > Geoffrey wrote: > > We had a vacuum fail recently with the following error: > > > > invalid page header in block 846 of relation "move_pkey" > > > > Anyone have an idea what could cause this problem and what we need to do > > to resolve it? > > > > Running on Red Hat Enterprise 3, postgres 7.4.13 > > Regarding the issue above, is it possible that re-indexing the database > could resolve the problem, since the error is related to an index. > move_pkey is an index on field recid. Yes, reindex might fix it. But more than likely there's a problem with your hardware somewhere, and it needs to be checked out carefully for problems. i.e. bad hard drive, memory, cpu, etc...