From: G. Anthony Reina <reina@nsi.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] ERROR: Unable to locate type oid 718 in catalog
Date: Tue, 31 Aug 1999 12:10:52 -0700
Message-ID: <37CC28BC.FA3D9BEC@nsi.edu> (raw)
References: <16230.936122891@sss.pgh.pa.us>
Tom Lane wrote:
> A quick glimpse says that the only occurrences of that error text are
> in parse_type.c, which is not code that I'd think would get called from
> vacuum. Odd.
>
> If you do "select * from pg_type where oid = 718;" you should get
>
> typname|typowner|typlen|typprtlen|typbyval|typtype|typisdefined|typdelim|typrelid|typelem|typinput |typoutput |typreceive|typsend |typalign|typdefault
> -------+--------+------+---------+--------+-------+------------+--------+--------+-------+---------+----------+----------+----------+--------+----------
> circle | 256| 24| 47|f |b |t |, | 0| 0|circle_in|circle_out|circle_in |circle_out|d |
> (1 row)
>
> If you don't then indeed pg_type is corrupted.
>
> regards, tom lane
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.
Any suggestions on a workaround? We'd really prefer to use 'circle' as a tablename and don't need it as a pg_type.
-Tony
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: reina@nsi.edu, tgl@sss.pgh.pa.us
Subject: Re: [HACKERS] ERROR: Unable to locate type oid 718 in catalog
In-Reply-To: <37CC28BC.FA3D9BEC@nsi.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox