Re: ERROR: cache lookup failed for relation 17442 (repost)

From: Michael Guerin <guerin(at)rentec(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: ERROR: cache lookup failed for relation 17442 (repost)
Date: 2005-02-07 22:42:35
Message-ID: 4207EEDB.6040006@rentec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2005-02-07 22:56:43 Re: ERROR: cache lookup failed for relation 17442 (repost)
Previous Message Tom Lane 2005-02-07 22:34:49 Re: ERROR: cache lookup failed for relation 17442 (repost)