Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Large Database \d: ERROR: cache lookup failed for relation ...
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Thomas F. O'Connell" <tf(at)o(dot)ptimized(dot)com>
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: Large Database \d: ERROR: cache lookup failed for relation ...
- Date: Thu, 24 May 2007 16:39:12 -0400
- Message-id: <20669(dot)1180039152(at)sss(dot)pgh(dot)pa(dot)us>
"Thomas F. O'Connell" <tf(at)o(dot)ptimized(dot)com> writes: > I'm dealing with a database where there are ~150,000 rows in > information_schema.tables. I just tried to do a \d, and it came back > with this: > ERROR: cache lookup failed for relation [oid] > Is this indicative of corruption, or is it possibly a resource issue? It'd not be unexpected if other transactions were concurrently dropping tables. If it's persistent (with the same OID mentioned) then you need to worry. regards, tom lane
- References:
- Large Database \d: ERROR: cache lookup failed for relation ...
- From: Thomas F. O'Connell
- Large Database \d: ERROR: cache lookup failed for relation ...
- Prev by Date: [Re] Re: [Re] Re: [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2
- Next by Date: Re: the future of pljava development
- Previous by thread: Large Database \d: ERROR: cache lookup failed for relation ...
- Next by thread: Return rows from function with expressions
- Indexes: