Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] ERROR: Unable to locate type oid 718 in catalog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "G(dot) Anthony Reina" <reina(at)nsi(dot)edu>
Cc: "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] ERROR: Unable to locate type oid 718 in catalog
Date: 1999-08-31 19:51:39
Message-ID: 16415.936129099@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"G. Anthony Reina" <reina(at)nsi(dot)edu> writes:
> Okay, I found out why I am getting this error. My partner is building
> a table which he is calling 'circle'. Of course, circle is a pg_type
> in the PostgreSQL. So he DROP TYPE'd circle from the database (we
> don't need that type anyway). For some reason, the database seems to
> not mind this until I do the vacuum analyze.

Is it possible that you've got tables lying around that have ordinary-
circle-type fields in them?  Vacuum analyze would notice the lack of
type data, but I'm not sure a plain vacuum would.

In any case, it'd be wise to flush everything in pg_operator and pg_proc
that has circle as an argument or result type.  (Does DROP TYPE do that
for you?  I bet not...)  There might be other system tables that have
references to circle, too.

			regards, tom lane

Responses

pgsql-hackers by date

Next:From: G. Anthony ReinaDate: 1999-08-31 20:20:35
Subject: Re: [HACKERS] ERROR: Unable to locate type oid 718 in catalog
Previous:From: The Hermit HackerDate: 1999-08-31 19:51:01
Subject: Re: [HACKERS] PostgreSQL 6.5.2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group