From: | "Wei Wu" <w(dot)wu(at)delcan(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | cache lookup failed for relation X |
Date: | 2008-03-07 16:10:03 |
Message-ID: | 19282688.1651204906203766.JavaMail.root@SCH-SMB2.sch.delcan.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I found some posts be developers discussing this issue last Jan. and Nov..
See link below.
http://search.postgresql.org/search?m=1&q=cache+lookup+failed+for+relation
&l=&d=&s=
But have not been able to find any suggestion on how an end user can use
to get around this problem. Basically, we have a table X, trying to drop
it would result an error message below:
cache lookup failed for relation XXXXX
I am using PgAdmin and I can still view the schema of this table, but
any operation on it would get the above error.
Any suggestion on how to drop a table in this situation.
I am also wondering whether this problem has been fixed in newer
PostgreSQL releases.
BTW, our postgreSQL version is 7.4.3.
Thanks.
____
This communication may contain information that is confidential, privileged or subject to copyright. If you are not the intended recipient, please advise by return e-mail and delete the message and any attachments immediately without reading, copying or forwarding to others.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Wurtz | 2008-03-07 16:20:56 | cache lookup failed for relation X |
Previous Message | Greg Smith | 2008-03-07 15:33:51 | Re: shared_buffers and shmmax what are the max recommended values? |