From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gunnar Sønsteby <gunnar(dot)sonsteby(at)netcom(dot)no>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cache lookup error |
Date: | 2009-11-13 15:08:45 |
Message-ID: | 20091113150845.GD4459@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard Huxton wrote:
> Tom Lane wrote:
> > Richard Huxton <dev(at)archonet(dot)com> writes:
> >> Gunnar Sønsteby wrote:
> >>> 2009-11-12 06:11:51 CET INSERTERROR: cache lookup failed for type 19218
> >
> >> So - something is trying to access a slony type via its old OID rather
> >> than its new one (or something like that). Not sure what this would be,
> >> since the drop-schema + cascade should have removed anything that could
> >> do this.
> >
> >> It's probably impossible to identify precisely what it was since it's
> >> not there any more.
> >
> > Well, there's still a reference to it somewhere in the system catalogs,
> > and locating the reference would give you a pretty good clue what it
> > was --- not to mention being a prerequisite step for cleaning up.
> > I'd try searching pg_class.reltype and pg_proc.prorettype for starters.
> > If no luck there, go through all the columns that are cited as linking
> > to pg_type.oid in
> > http://www.postgresql.org/docs/8.3/static/catalogs.html
>
> I was thinking it was a reference inside a function or similar. I'm
> guessing "compiled" plpgsql is opaque?
That doesn't persist across a restart, though.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2009-11-13 15:37:32 | Re: Libpq binary mode SELECT ... WHERE ID IN ($1) Question |
Previous Message | Marek Peca | 2009-11-13 15:07:09 | Re: PGconn gets frozen ocassionally after select() timeout |