Date: Sat, 3 Apr 2010 13:04:57 -0400
From: "justin@magwerks.com" <justin@magwerks.com>
Subject: Re: ERROR: cache lookup failed for relation X
To: "raghavendra t" <raagavendra.rao@gmail.com>,
	"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Message-Id: <17045727200882@mail.magwerks.com>
In-Reply-To: <h2xbc7de5a31004030938v82d1c243k27be011f9a681f76@mail.gma il.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="==_17045764700884/mail.magwerks.com==_"

This is a MIME-encapsulated message

--==_17045764700883/mail.magwerks.com==_
Content-Type: multipart/alternative;
 boundary="==_17045764700884/mail.magwerks.com==_"


--==_17045764700884/mail.magwerks.com==_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 from Postgresql to Return when it can't=
 find the table??? 

In the future please don't cross post to multiple lists.  

---- Message from mailto:raagavendra.rao@gmail.com raghavendra t=
 raagavendra.rao@gmail.com at 04-03-2010 10:08:11 PM ------


step 6 - Issue the commit in Session A 

postgres=3D# commit; 

Step -7 nowwe can the see the error in the session B 

ERROR: cache lookup failed for relation X 

Could plese tell me, why this is generated and what is the cause.


Thanks in advance 

Regards 
Raghavendra 


All legitimate Magwerks Corporation quotations are sent in a .PDF file=
 attachment with a unique ID number generated by our proprietary quotation=
 system. Quotations received via any other form of communication will not=
 be honored.

CONFIDENTIALITY NOTICE: This e-mail, including attachments, may contain=
 legally privileged, confidential or other information proprietary to=
 Magwerks Corporation and is intended solely for the use of the individual=
 to whom it addresses. If the reader of this e-mail is not the intended=
 recipient or authorized agent, the reader is hereby notified that any=
 unauthorized viewing, dissemination, distribution or copying of this=
 e-mail is strictly prohibited. If you have received this e-mail in error,=
 please notify the sender by replying to this message and destroy all=
 occurrences of this e-mail immediately.
Thank you.

--==_17045764700884/mail.magwerks.com==_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html><head><style><!-- P{ margin-top:0;margin-bottom:0;} //=
 --></style></head><body><span style=3D"font-family: Arial; color: rgb(0,=
 0, 0);">Because You dropped/deleted the table cache in Session A.&nbsp;=
 <br><br>The simplest way to look at it is&nbsp; Session B was lock out=
 when the Drop table command was issued from Session A.&nbsp; Now when=
 session B finally got its chance to drop/delete the table it was already=
 gone .<br><br>What kind error were you expecting from Postgresql to Return=
 when it can't find the table??? <br><br>In the future please&nbsp; don't=
 cross post to multiple lists. &nbsp; <br><br>---- Message from <a=
 href=3D"mailto:raagavendra.rao@gmail.com">raghavendra t=
 &lt;raagavendra.rao@gmail.com&gt;</a> at 04-03-2010 10:08:11 PM=
 ------<blockquote style=3D"border-left: 2px solid rgb(0, 0, 0);=
 padding-left: 5px; margin-left: 5px;"><br><div>step 6 - Issue the commit=
 in Session A</div>
<div>&nbsp;</div>
<div>postgres=3D# commit;</div>
<div>&nbsp;</div>
<div>Step -7 now&nbsp;we can the see the error in the session B</div>
<div>&nbsp;</div>
<div>ERROR: cache lookup failed for relation X</div>
<div><br>Could plese tell me, why this is generated and what is the=
 cause.<br></div>
<div>&nbsp;</div>
<div>Thanks in advance</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Raghavendra</div>

</blockquote></span><br>
All legitimate Magwerks Corporation quotations are sent in a .PDF file=
 attachment with a unique ID number generated by our proprietary quotation=
 system. Quotations received via any other form of communication will not=
 be honored.
<BR>

<BR>

CONFIDENTIALITY NOTICE: This e&#045;mail&#044; including attachments&#044;=
 may contain legally privileged&#044; confidential or other information=
 proprietary to Magwerks Corporation and is intended solely for the use of=
 the individual to whom it addresses. If the reader of this e&#045;mail is=
 not the intended recipient or authorized agent&#044; the reader is hereby=
 notified that any unauthorized viewing&#044; dissemination&#044;=
 distribution or copying of this e&#045;mail is strictly prohibited. If you=
 have received this e&#045;mail in error&#044; please notify the sender by=
 replying to this message and destroy all occurrences of this e&#045;mail=
 immediately.
<BR>

Thank you.
<BR>

</body></html>


--==_17045764700884/mail.magwerks.com==_--
--==_17045764700883/mail.magwerks.com==_--