From: Tom Lane <tgl@sss.pgh.pa.us>
To: Darren Reed <darrenr+postgres@fastmail.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: postgres 8.2.6 core dump when initialising.
Date: Mon, 14 Apr 2008 10:32:42 -0400
Message-ID: <2155.1208183562@sss.pgh.pa.us> (raw)
In-Reply-To: <48036459.7040503@fastmail.net>
References: <4802F108.2090709@fastmail.net>
<1071.1208179948@sss.pgh.pa.us>
<48036459.7040503@fastmail.net>
Darren Reed <darrenr+postgres@fastmail.net> writes:
> Some time ago I saw this message:
> ERROR: index "pg_depend_reference_index" contains unexpected zero page
> at block 23
> HINT: Please REINDEX it.
> ERROR: index "table_p_hash_idx" contains unexpected zero page at block 7
> HINT: Please REINDEX it.
[ squint... ] If something is randomly zeroing out pages, and it
happens to hit pg_class, that could explain your troubles. Maybe
you are dealing with a kernel bug or flaky hardware.
>> It might be useful if we could look at a pg_filedump dump of your
>> pg_class table, too.
> How do I know which one is pg_class?
It'd be $PGDATA/base/NNN/1259 where NNN is the OID of the broken
database. With a dead system the easiest way to find out that OID
is to look at the text file $PGDATA/global/pg_database --- the
first number after a database's name is its OID.
I find that "pg_filedump -i -f FILENAME" gives the most useful output.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, darrenr+postgres@fastmail.net
Subject: Re: postgres 8.2.6 core dump when initialising.
In-Reply-To: <2155.1208183562@sss.pgh.pa.us>
* 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