Hi,
I had a similar problem and overcame it by temporarily setting
zero_damaged_pages, then doing a full vacuum and re-index on the affected table.
The rows contained in the corrupted page were lost but the rest of the table
was OK after this.
Regards // Mike
-Original Message-
From:
Hi,
Am not sure if this is something we've done wrong or maybe a bug.
Whenever any kind of query is done on the table below, this is the
result:
ispdb_vxe=> select * from pm.carrier_on_13642;
ERROR: cache lookup failed for type 0
I first noticed it when I noticed that the regular backups were
. I will try to locate the corrupted row(s), maybe
pg_filedump can help with that.
Regards // Mike
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Saturday, 26 May 2007 9:38 AM
To: Michael Harris (BR/EPA)
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] ERROR: cache
,
complaining about another table pm.carrier_oo_13642 with the same error.
I then excluded that table also, after which the dump succeeded.
What does "ERROR: cache lookup failed for type 0" mean? I searched all
over the place for a good descripion but could not find one.
Regards // Mike
---
Hi,
Am not sure if this is something we've done wrong or maybe a bug.
Whenever any kind of query is done on the table below, this is the
result:
ispdb_vxe=> select * from pm.carrier_on_13642;
ERROR: cache lookup failed for type 0
I first noticed it when I noticed that the regular backups were
