From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Bradley Holbrook" <operations_bradley(at)servillian(dot)ca> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Drop Schema Error |
Date: | 2011-01-29 16:57:55 |
Message-ID: | 12066.1296320275@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Bradley Holbrook" <operations_bradley(at)servillian(dot)ca> writes:
> DROP SCHEMA "_old_permissions" CASCADE;
> NOTICE: drop cascades to 2 other objects
> DETAIL: drop cascades to function 17059
> drop cascades to function 17060
> [Err] ERROR: cache lookup failed for function 17060
> What is this trying to tell me?
Apparently you've got some dangling references in pg_depend, ie those
functions were dropped already but the pg_depend entries for them were
not cleaned up.
We've heard similar reports before (usually about temp tables not
functions, IIRC) but never been able to reproduce them or identify a
cause. What PG version is this? Have you done anything funny to that
schema or its contents, or had any crashes around the time of
manipulating either?
As far as cleaning up goes, the thing to do would be to manually delete
the relevant pg_depend entries --- for this one, an entry with objid =
17060 is probably what you're looking for. But it would be good to try
to figure out how you got into this state first.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Viktor Bojović | 2011-01-29 19:15:55 | Re: Drop Schema Error |
Previous Message | Bradley Holbrook | 2011-01-28 23:53:59 | Drop Schema Error |