Re: Strange database corruption with PostgreSQL 7.4.x o - Mailing list pgsql-general

From Matthias.Pitzl@izb.de
Subject Re: Strange database corruption with PostgreSQL 7.4.x o
Date
Msg-id 11EC9A592C31034C88965C87AF18C2A70CFC5B@m0000s61
Whole thread Raw
Responses Re: Strange database corruption with PostgreSQL 7.4.x o n Debian Sarge  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hello Tom!

Not yet, but i will try this one too. Anything special i should look for
when dumping out the bad pages?

-- Matthias

> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane
> Sent: Wednesday, September 20, 2006 4:32 PM
> To: Matthias.Pitzl@izb.de
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Strange database corruption with
> PostgreSQL 7.4.x on Debian Sarge
>
>
> Matthias.Pitzl@izb.de writes:
> > invalid page header in block 437702 of relation "xxxx"
>
> I concur with Scott that this sounds suspiciously like a hardware
> problem ... but have you tried dumping out the bad pages with
> pg_filedump or even just od?  The pattern of damage would help to
> confirm or disprove the theory.
>
> You can find pg_filedump source code at
> http://sources.redhat.com/rhdb/
>
>             regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Memory efficient insertion/retrieval of bytea
Next
From: "Harry Hehl"
Date:
Subject: pg_dump output containing CREATE TYPE does not restore with psql