Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific)
Date
Msg-id 595887.1718984150@sss.pgh.pa.us
Whole thread Raw
In response to Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific)  (Eric Marsden <eric.marsden@risk-engineering.org>)
Responses Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) / user error
List pgsql-bugs
Eric Marsden <eric.marsden@risk-engineering.org> writes:
> I see a PostgreSQL error "cache lookup failed for type 34813" after the
> following sequence of network requests over a single network connection
> to PostgreSQL (which is otherwise idle):

> CREATE TYPE rating AS ENUM('ungood', 'good')
> CREATE TABLE act(name TEXT, value RATING)
> INSERT INTO act VALUES('thoughtcrime', 'ungood') -- OK
> INSERT INTO act VALUES('blackwhite', $1) -- with $1 = "good" / type oid for "rating" / text format

Interesting.  To clarify, are these commands run within a single
transaction, and if not where are the transaction boundaries?

Would you run this under log_error_verbosity = verbose and post the
full postmaster log entry for the failure, especially the LOCATION
data?  (Even better would be a stack trace from the errfinish call,
but perhaps LOCATION will be enough.)

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18518: ::timestamp add minutes and seconds to the converted values
Next
From: Eric Marsden
Date:
Subject: Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) / user error