From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kevin Kempter <kevink(at)consistentstate(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: drop table error |
Date: | 2009-10-08 18:09:19 |
Message-ID: | 27353.1255025359@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Kevin Kempter <kevink(at)consistentstate(dot)com> 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 <databasename>"
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
From | Date | Subject | |
---|---|---|---|
Next Message | raghu ram | 2009-10-08 20:32:19 | Re: postgres 8.3.8 and Solaris 10 problems? |
Previous Message | Kevin Kempter | 2009-10-08 17:53:00 | drop table error |