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 18:08:11 |
Message-ID: | 16230.936122891@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"G. Anthony Reina" <reina(at)nsi(dot)edu> writes:
> Anyone run into this error before:
> ERROR: Unable to locate type oid 718 in catalog
> This occurred when I tried to 'vacuum verbose analyze' my database.
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
From | Date | Subject | |
---|---|---|---|
Next Message | fjcuberos | 1999-08-31 18:30:00 | |
Previous Message | Tom Lane | 1999-08-31 17:51:11 | Re: [HACKERS] PostgreSQL 6.5.2 |