| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Carlo Curatolo *EXTERN*" <genamiga(at)brutele(dot)be>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Invalid Page Header Error |
| Date: | 2013-10-16 09:32:16 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17C4A69B@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Carlo Curatolo wrote:
> SELECT oid, relname, relkind FROM pg_class WHERE relfilenode = 599662; -->
> returns nothing.
Maybe the wrong database?
Try to find out which object this file belongs to (maybe with oid2name).
> No crash occurs, I have tested the hardware (memory, harddisks, RAID5,
> stability test...)
Good.
> I have made a little program to read all the LargeObject of my tables, they
> are all readable.
Good.
> So, I restart postgreSQL with "zero_damaged_pages = on", lauch a vacuumlo
> and vacummdb, restart with "zero_damaged_pages = off", the recheck all the
> LargeObject of my tables.
You mean, you ran pg_dumpall, created a new cluster and imported, right?
If you continue running the damaged cluster, the next problem
is waiting just around the bend.
> The error do no occurs anymore...
>
> Seems that the corrupted LargeObject was not used...possible ?
I maintain that it was a table or index that was corrupted, not
a large object.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carlo Curatolo | 2013-10-16 10:13:30 | Re: Invalid Page Header Error |
| Previous Message | Carlo Curatolo | 2013-10-16 08:11:26 | Re: Invalid Page Header Error |