From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Keaton Adams <Keaton_Adams(at)McAfee(dot)com> |
Cc: | V S P <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cache lookup failed for relation message in PG 8.3.7 |
Date: | 2010-02-11 15:49:45 |
Message-ID: | 9801.1265903385@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Keaton Adams <Keaton_Adams(at)McAfee(dot)com> writes:
> Any ideas why we would be receiving this cache lookup failed message?
> PostgreSQL 8.3.7 64 bit, RHEL 5 64 bit OS
> [ query applying pg_table_is_visible() to most of pg_class ]
Is it repeatable, or just something that shows up occasionally with
different OIDs mentioned? If the latter, it's probably a known race
condition against table drops: the pg_class scan can find rows that
belong to tables that are already deleted by the time
pg_table_is_visible gets called. There's a hack in 8.4 to avoid
the errors by having pg_table_is_visible (and related functions)
return null instead of failing, but I don't believe we changed it
in previous releases.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2010-02-11 15:52:39 | Re: Postgres Triggers issue |
Previous Message | Tom Lane | 2010-02-11 15:39:04 | Re: Extending SQL in C using VARIABLE length type |