Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific)
| От | Tom Lane |
|---|---|
| Тема | Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) |
| Дата | |
| Msg-id | 595887.1718984150@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) (Eric Marsden <eric.marsden@risk-engineering.org>) |
| Ответы |
Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) / user error
|
| Список | 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 по дате отправления: