Carlo Curatolo wrote:
> Yes I ran pg_dumpall, create a new cluster and import.
Ok, cool.
> Everything seems fine now.
>
> How can I prevent that ?
Prevent data corruption?
Have good hardware, run the latest PostgreSQL fixes...
Most of all, have a good backup so that you can recover.
Yours,
L
Yes I ran pg_dumpall, create a new cluster and import.
Everything seems fine now.
How can I prevent that ?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Invalid-Page-Header-Error-tp1925403p5774728.html
Sent from the PostgreSQL - general mailing list archive at Nabbl
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,
> stabi
Thanks for the help.
SELECT oid, relname, relkind FROM pg_class WHERE relfilenode = 599662; -->
returns nothing.
No crash occurs, I have tested the hardware (memory, harddisks, RAID5,
stability test...)
I have made a little program to read all the LargeObject of my tables, they
are all readable.
Carlo Curatolo wrote:
> When I lauch a vacuumdb, I have an error : ERREUR: en-tête de page invalide
> dans le bloc 39639 de la relation base/16384/599662
>
> With a
> SELECT * FROM pg_catalog.pg_largeobject
>
> Result is
> ERREUR: en-tête de page invalide dans le bloc 39639 de la relation
> bas
I have quite the same problem.
When I lauch a vacuumdb, I have an error : ERREUR: en-tête de page invalide
dans le bloc 39639 de la relation base/16384/599662
With a
SELECT * FROM pg_catalog.pg_largeobject
Result is
ERREUR: en-tête de page invalide dans le bloc 39639 de la relation
base/163
Hello Richard,
Just to keep you informed...
Richard Huxton a écrit :
>> We had a server crash and when restarting postgres it works, except some
>> "Invalid Page Header Error" :
>
> Data corrupted on disk. Either:
> 1. You have bad hardware
> 2. You have disks lying about fsync
> 3. You have fsy
Denis BUCHER wrote:
> Hello,
>
> We had a server crash and when restarting postgres it works, except some
> "Invalid Page Header Error" :
Data corrupted on disk. Either:
1. You have bad hardware
2. You have disks lying about fsync
3. You have fsync turned off.
> I already try VACUUM / FULL / ANA
Hello,
We had a server crash and when restarting postgres it works, except some
"Invalid Page Header Error" :
I already try VACUUM / FULL / ANALYSE but same error
Even when doing a pg_dumpall, we have this problem.
$ pg_dumpall >/dev/null
pg_dump: ERREUR: en-tête de page invalide dans le bloc
