From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Eric Marsden <eric(dot)marsden(at)risk-engineering(dot)org> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) |
Date: | 2024-06-21 15:35:50 |
Message-ID: | 595887.1718984150@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Eric Marsden <eric(dot)marsden(at)risk-engineering(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Marsden | 2024-06-21 16:16:53 | Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) / user error |
Previous Message | Tom Lane | 2024-06-21 14:50:26 | Re: BUG #18518: ::timestamp add minutes and seconds to the converted values |