From: | Mark Gibson <gibsonm(at)cromwell(dot)co(dot)uk> |
---|---|
To: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Cache lookup failed for relation, when trying to DROP TABLE. |
Date: | 2004-10-06 14:49:37 |
Message-ID: | 09eb1183a614c359246a374703d6a97741640612@cromwell.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
I've just encountered a problem that I don't know how to deal with.
After having a play with SlonyI, I dropped the entire slony cluster
schema, and then tried to drop a schema which held some slave tables
for the slony cluster.
I kept getting the following error:
ERROR: cache lookup failed for relation 4667548
So, I cleared out everything I could manually from the schema,
leaving four remaining tables that refuse to be dropped, giving
the error above (the relation oid varies though).
Anyone know what this means?
Is there a way to forcefully remove these tables and the schema
using the pg_catalog tables?
Is there any other information I should provide that may help?
Specs:
Redhat Enterprise Linux 3
PostgreSQL 7.4.5
Slony-I 1.0.2
Cheers
--
Mark Gibson <gibsonm |AT| cromwell |DOT| co |DOT| uk>
Web Developer & Database Admin
Cromwell Tools Ltd.
Leicester, England.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2004-10-06 14:56:54 | Re: Random not so random |
Previous Message | Jimmie H. Apsey | 2004-10-06 14:35:50 | Re: Verifying Referential Integrity |