Hi All,
I've been getting these errors ("ERROR: cache lookup failed for
relation 17442") in my logs for a while now. It originally seemed
like a hardware problem, however now we getting them pretty consistently
on a couple servers. I've scalled down the schema to the one table and
the fu
Tom Lane wrote:
Michael Guerin <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
What was the "original function" exactly?
It's included in the schema call uspgetcompositeids2_orig. The only
differences is that this function creates and drops the temp table
wit
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"
Wha
Hi All,
I've been getting these errors ("ERROR: cache lookup failed for
relation 17442") in my logs for a while now. It originally seemed
like a hardware problem, however now we getting them pretty consistently
on a couple servers. I've scalled down the schema to the one table and
the funct
