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
within the function, the new
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
> within the function, the newer function keep
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
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Mon, Feb 07, 2005 at 05:07:47PM -0500, Tom Lane wrote:
>> A more general issue is that we now have a pile of "catalog inquiry"
>> functions that all make use of backend internal lookups and therefore
>> reflect SnapshotNow behavior to the user.
> Can
On Mon, Feb 07, 2005 at 05:07:47PM -0500, Tom Lane wrote:
> A more general issue is that we now have a pile of "catalog inquiry"
> functions that all make use of backend internal lookups and therefore
> reflect SnapshotNow behavior to the user. This has bothered me for
> some
> time,
Can we pass
Michael Guerin wrote:
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 o
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 "ori
Michael Guerin <[EMAIL PROTECTED]> writes:
> I've been getting these errors ("ERROR: cache lookup failed for
> relation 17442") in my logs for a while now.
Turning on verbose error logging shows that the error invariably comes
from RelationIsVisible():
2005-02-07 16:44:35 EST 2994 ERROR: X
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
10 matches
Mail list logo
