From: | Dave Wurtz <dave_wurtz(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | cache lookup failed for relation X |
Date: | 2008-03-07 16:20:56 |
Message-ID: | 352858.14686.qm@web45908.mail.sp1.yahoo.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.
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
From | Date | Subject | |
---|---|---|---|
Next Message | Anton Melser | 2008-03-07 16:27:22 | Re: shared_buffers and shmmax what are the max recommended values? |
Previous Message | Wei Wu | 2008-03-07 16:10:03 | cache lookup failed for relation X |