>
> Hi Justin,
Thank you for your reply..
> In the future please don't cross post to multiple lists.
Appoligies for it...
Regards
Raghavendra
On Sat, Apr 3, 2010 at 10:34 PM, jus...@magwerks.com
wrote:
> Because You dropped/deleted the table cache in Session A.
>
> The simplest way to loo
Hi Tom,
Thank you for your Prompt reply..
Am getting this error only in the application level that too with multiple
sessions. By getting that error am assuming that the table has got dropped
in some other session.
I understood from here is that its not a serious problem to catalog
Corruption.
Re
raghavendra t writes:
> I am facing the error "cache lookup failed for relation X" in Postgres-8.4.2
> [ when dropping the same table concurrently in two sessions ]
> Could plese tell me, why this is generated and what is the cause.
>From the perspective of session B, the table disappeared after
Because You dropped/deleted the table cache in Session A.
The simplest way to look at it is Session B was lock out when the Drop table
command was issued from Session A. Now when session B finally got its chance to
drop/delete the table it was already gone .
What kind error were you expecting f
Hi All,
I am facing the error "cache lookup failed for relation X" in Postgres-8.4.2
version. As you all know, its a reproducable and below is the example.
This can be generated with two sessions;
Am opening two sessions here Session A and Session B
Session A
=
step 1 - creating the table
joe speigle <[EMAIL PROTECTED]> writes:
> List and (most importantly) somebody with the same problem,
> I finally got access to my table by performing these random steps:
> ...
> happily, there is no visible bad news even on running "\set verbosity verbose"
Dump, initdb, reload. Do NOT assume tha
o: pgsql-general@postgresql.org
Sent: Monday, September 8, 2008 9:54:36 PM
Subject: [GENERAL] ERROR: cache lookup failed for relation
Hello list,
I have contributed the mysql2pgsql script to the community at
http://pgfoundry.org/projects/mysql2pgsql/
I am wondering why I pg_class can see
Hello list,
I have contributed the mysql2pgsql script to the community at
http://pgfoundry.org/projects/mysql2pgsql/
I am wondering why I pg_class can see it, but " AND
pg_catalog.pg_table_is_visible(c.oid)" (as in \d korean_english)
queries are returning false. My database has been acting
Joe Markwardt <[EMAIL PROTECTED]> writes:
>> The next thing to check is whether the OID mentioned in pg_trigger
>> (which I forgot already) is the same as the OID shown in pg_class, ie
>> select oid from pg_class where relname = 'pl02_status_table'.
> oid
> ---
> 438094756
> (1 row)
> T
On Wed, 2005-07-06 at 23:36 -0400, Tom Lane wrote:
> Joe Markwardt <[EMAIL PROTECTED]> writes:
> > On Wed, 2005-07-06 at 14:04 -0400, Tom Lane wrote:
> >> They appear to be triggers for a foreign-key constraint between
> >> pl_inventory_analyzer_files_table and pl02_status_table ... so I guess
> >
Joe Markwardt <[EMAIL PROTECTED]> writes:
> On Wed, 2005-07-06 at 14:04 -0400, Tom Lane wrote:
>> They appear to be triggers for a foreign-key constraint between
>> pl_inventory_analyzer_files_table and pl02_status_table ... so I guess
>> the question is what happened to the latter?
> I'm not sur
On Wed, 2005-07-06 at 14:04 -0400, Tom Lane wrote:
> Joe Markwardt <[EMAIL PROTECTED]> writes:
> >>> I am getting this error "ERROR: cache lookup failed for relation
> >>> 438095645" when i try to run "drop table
> >>> pl_inventory_analyzer_files_table ;" from psql on the database server.
> >>
>
Joe Markwardt <[EMAIL PROTECTED]> writes:
>>> I am getting this error "ERROR: cache lookup failed for relation
>>> 438095645" when i try to run "drop table
>>> pl_inventory_analyzer_files_table ;" from psql on the database server.
>>
>> Look through the system catalogs to see where that OID appea
On Wed, 2005-07-06 at 11:20 -0400, Tom Lane wrote:
> Joe Markwardt <[EMAIL PROTECTED]> writes:
> > I am getting this error "ERROR: cache lookup failed for relation
> > 438095645" when i try to run "drop table
> > pl_inventory_analyzer_files_table ;" from psql on the database server.
>
> Look
Joe Markwardt <[EMAIL PROTECTED]> writes:
> I am getting this error "ERROR: cache lookup failed for relation
> 438095645" when i try to run "drop table
> pl_inventory_analyzer_files_table ;" from psql on the database server.
Look through the system catalogs to see where that OID appears.
pg
Hey list,
I am getting this error "ERROR: cache lookup failed for relation
438095645" when i try to run "drop table
pl_inventory_analyzer_files_table ;" from psql on the database server.
I've already REINDEX'd the database system tables, and all the indexes
on that table, and on all the in
i tried running postgres and did a reindex..
and i got this..
...
NOTICE: relation 16596 was reindexed
NOTICE: relation 16598 was reindexed
NOTICE: relation 16384 was reindexed
NOTICE: relation 16386 was reindexed
NOTICE: relation 1262 was reindexed
ERROR: Cannot create uniq
17 matches
Mail list logo
