| From: | Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> |
|---|---|
| To: | slony1-general(at)lists(dot)slony(dot)info |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | ERROR: XX000: cache lookup failed for relation |
| Date: | 2008-04-04 14:05:18 |
| Message-ID: | 498765.17802.qm@web25813.mail.ukl.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi chaps,
I've got a problem trying to drop a table, I get the error "cache lookup failed for relation"
SEE=# drop table replicated_users;
ERROR: XX000: cache lookup failed for relation 30554884
LOCATION: getRelationDescription, dependency.c:2021
Now this table is on a slony-I slave and was in replication when I tried to drop it - I presume this is a big mistake and I should never try to drop a table without first droping it from replication?
In addition I'd set up a trigger on the table "replicate_users".
If I do:
select relname,oid from pg_class where relname = 'replicated_users';
-[ RECORD 1 ]-------------
relname | replicated_users
oid | 30554879
Thats not the same oid as the one it's complaining about.
Does anyone have any idea why this has happened or how I can fix it?
Cheers
Glyn
___________________________________________________________
Yahoo! For Good helps you make a difference
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tino Wildenhain | 2008-04-04 14:05:45 | Re: Secure "where in(a,b,c)" clause. |
| Previous Message | Aidan Van Dyk | 2008-04-04 13:49:40 | Re: modules |