From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Geoffrey <esoteric@3times25.net>
Cc: pgsql-admin@postgresql.org, pgsql general <pgsql-general@postgresql.org>
Subject: Re: vacuum fails with 'invalid page header' message
Date: Fri, 05 Jan 2007 16:21:34 -0600
Message-ID: <1168035694.3421.52.camel@state.g2switchworks.com> (raw)
In-Reply-To: <459ECEE8.5030806@3times25.net>
References: <459EC34E.3070304@3times25.net>
<459ECEE8.5030806@3times25.net>
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...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, esoteric@3times25.net, pgsql-general@postgresql.org
Subject: Re: vacuum fails with 'invalid page header' message
In-Reply-To: <1168035694.3421.52.camel@state.g2switchworks.com>
References: <459EC34E.3070304@3times25.net> <459ECEE8.5030806@3times25.net> <1168035694.3421.52.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox