drop table error

drop table error

am 08.10.2009 19:53:00 von Kevin Kempter

--Boundary-01=_8bizKnsa0W0ivfw
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all;

anyone know what would cause errors like this (postgres version 8.1.15):



drop table bigtab1;
ERROR: could not find tuple for constraint 373617



drop sequence bigtab2_id_seq;
ERROR: cache lookup failed for relation 371698

Thanks in advance...

--Boundary-01=_8bizKnsa0W0ivfw
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: 7bit



Hi all;



anyone know what would cause errors like this (postgres version 8.1.15):





drop table bigtab1;


ERROR: could not find tuple for constraint 373617





drop sequence bigtab2_id_seq;


ERROR: cache lookup failed for relation 371698



Thanks in advance...


--Boundary-01=_8bizKnsa0W0ivfw--

Re: drop table error

am 08.10.2009 20:09:19 von Tom Lane

Kevin Kempter writes:
> anyone know what would cause errors like this (postgres version 8.1.15):
> drop table bigtab1;
> ERROR: could not find tuple for constraint 373617
> drop sequence bigtab2_id_seq;
> ERROR: cache lookup failed for relation 371698

Looks like system catalog corruption to me. If you're lucky it's only
index corruption and you could fix it with "REINDEX SYSTEM "

I seem to recall that you've had a LOT of stability problems in the
recent past. I'm thinking that there is some underlying problem
with your system -- maybe bad hardware or a nasty kernel bug.
If Postgres were this unstable for everybody, nobody would use it.

regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin