| From: | Phil Sorber <phil(at)omniti(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: objects tied to missing extension |
| Date: | 2011-11-28 21:14:41 |
| Message-ID: | CADAkt-hZBfpW2tLLm_XC942M0ULVrZ_ipi1j_+sBvDONSuzPdg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Nov 28, 2011 at 4:10 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Phil Sorber <phil(at)omniti(dot)com> writes:
>> I am still able to reproduce the "ERROR: cache lookup failed for extension
>> xxxxx" if I use an explicit 'drop extension'. I am unsure how I can
>> reverse the state it is now in. I assume there is some system catalog
>> I can edit that will fix it?
>
> I think you have some dangling entries in pg_depend --- manually
> deleting any rows that reference the missing pg_extension OID should fix
> it.
>
> regards, tom lane
>
That fixes it. At least I have a workaround for current installs.
Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Boguk | 2011-11-28 21:54:30 | Re: BUG #6307: intarray extention gin index does not work with Hot standby |
| Previous Message | Tom Lane | 2011-11-28 21:10:11 | Re: objects tied to missing extension |