Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 53D3F9FA315; Sat, 6 Jan 2007 06:01:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 23269-01; Sat, 6 Jan 2007 06:01:41 -0400 (AST) X-Greylist: delayed 11:42:17.500593 by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from www.3times25.net (duck.3times25.net [66.23.211.34]) by postgresql.org (Postfix) with ESMTP id F316C9FA311; Sat, 6 Jan 2007 06:01:40 -0400 (AST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by www.3times25.net (Postfix) with ESMTP id 686465401E; Sat, 6 Jan 2007 05:01:37 -0500 (EST) Message-ID: <459F7381.6020208@3times25.net> Date: Sat, 06 Jan 2007 05:01:37 -0500 From: Geoffrey User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: pgsql-admin@postgresql.org, pgsql general Subject: Re: vacuum fails with 'invalid page header' message References: <459EC34E.3070304@3times25.net> <459ECEE8.5030806@3times25.net> <1168035694.3421.52.camel@state.g2switchworks.com> In-Reply-To: <1168035694.3421.52.camel@state.g2switchworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/53 X-Sequence-Number: 24209 Scott Marlowe wrote: > 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... After reindexing the table, vacuum full completes successfully. Would this be an indication the reindexing corrected the problem? Anything else the could possibly cause this problem? The sys admin is doubtful it's hardware related. We don't see any errors in the system logs to indicate there's a problem. Is it possible that our application could cause such corruption? -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin