Re: ERROR: cache lookup failed for relation 17442 (repost) - Mailing list pgsql-bugs

From Michael Guerin
Subject Re: ERROR: cache lookup failed for relation 17442 (repost)
Date
Msg-id 4207EEDB.6040006@rentec.com
Whole thread Raw
In response to Re: ERROR: cache lookup failed for relation 17442 (repost)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ERROR: cache lookup failed for relation 17442 (repost)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane wrote:

>Also ... the visibility issue doesn't seem to explain the other symptom
>you reported:
>
>
>
>>With the original function, the log messages were slightly different and
>>usually caused the server to reset:
>>ERROR:  duplicate key violates unique constraint
>>"pg_type_typname_nsp_index"
>>
>>
>
>What was the "original function" exactly?
>
>            regards, tom lane
>
>
It's included in the schema call uspgetcompositeids2_orig.   The only
differences is that this function creates and drops the temp table
within the function, the newer function keeps the temp table around for
the life of the connections.

-michael

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: ERROR: cache lookup failed for relation 17442 (repost)
Next
From: Tom Lane
Date:
Subject: Re: ERROR: cache lookup failed for relation 17442 (repost)