>
> 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
