Re: Strange database corruption with PostgreSQL 7.4.x o

From: Matthias(dot)Pitzl(at)izb(dot)de
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Strange database corruption with PostgreSQL 7.4.x o
Date: 2006-09-20 14:40:35
Message-ID: 11EC9A592C31034C88965C87AF18C2A70CFC5B@m0000s61
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: Wednesday, September 20, 2006 4:32 PM
> To: Matthias(dot)Pitzl(at)izb(dot)de
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Strange database corruption with
> PostgreSQL 7.4.x on Debian Sarge
>
>
> Matthias(dot)Pitzl(at)izb(dot)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
>

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Murphy 2006-09-20 14:43:12 Getting prepared statement parameters in log when using JDBC with PG 8
Previous Message Tom Lane 2006-09-20 14:38:19 Re: Memory efficient insertion/retrieval of bytea