Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 1D996634254; Sat, 3 Apr 2010 23:52:14 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 50911-04; Sun, 4 Apr 2010 02:51:53 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pw0-f46.google.com (mail-pw0-f46.google.com [209.85.160.46]) by mail.postgresql.org (Postfix) with ESMTP id 88A1663499D; Sat, 3 Apr 2010 23:52:02 -0300 (ADT) Received: by pwi5 with SMTP id 5so2289490pwi.19 for ; Sat, 03 Apr 2010 19:52:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=XoyuekJpXXDtO2EfqhdN/y7kDFMHaQdfXDBkRdBV37I=; b=swCfPcH+LGi30QAlCxw/6vkNSVPDxShUbCixzJGcz0YIa1/wdQHGYeiAIuLgD+EcSn iEIgVuygYLrXEhtJ7TJ7PCOoK2hWDWMZN0TwdLdsHluXIXo2x3a+mdlXyy5IpqmW8nmk tluAe4m6QlMjN8EL/L1l2YiSUZp5i9NhcoMak= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=sNpPw3r+gU3DsV4lEXVjGNFX8ZogPpHZQWkK41Rs+n+kCsuwaX0orWiVs5O+SBSzWG tRnuRLljS3J7LHFA2tUl+FCYVG8Q5wYrRpQcOpACASkIdVO7hIuYn4XKNYkT8DARaDK0 TsnuckwmWYvgJow/FWGRe1DNN/uxSMGgsOzRo= MIME-Version: 1.0 Received: by 10.140.178.4 with HTTP; Sat, 3 Apr 2010 19:52:00 -0700 (PDT) In-Reply-To: <17045727200882@mail.magwerks.com> References: <17045727200882@mail.magwerks.com> Date: Sun, 4 Apr 2010 08:22:00 +0530 Received: by 10.140.58.18 with SMTP id g18mr2764179rva.46.1270349520463; Sat, 03 Apr 2010 19:52:00 -0700 (PDT) Message-ID: Subject: Re: ERROR: cache lookup failed for relation X From: raghavendra t To: "justin@magwerks.com" Cc: "pgsql-general@postgresql.org" , "pgsql-performance@postgresql.org" Content-Type: multipart/alternative; boundary=001636b2b030e868270483604b24 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.391 tagged_above=-10 required=5 tests=AWL=-1.207, BAYES_40=-0.185, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201004/148 X-Sequence-Number: 161346 --001636b2b030e868270483604b24 Content-Type: text/plain; charset=ISO-8859-1 > > 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, justin@magwerks.com wrote: > 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 raghavendra t at 04-03-2010 10:08:11 PM ------ > > > step 6 - Issue the commit in Session A > > postgres=# commit; > > Step -7 now we 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. > > --001636b2b030e868270483604b24 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Justin,
=A0
Thank you for your reply..
=A0
In the future please=A0 don'= t cross post to multiple lists.=A0=A0
=A0
Appoligies for it...
=A0
Regards
Raghavendra
=A0
On Sat, Apr 3, 2010 at 10:34 PM, justin@magwerks.com <justin@magwerks.com> wrote:= =20
=A0
Because You drop= ped/deleted the table cache in Session A.=A0=20
=A0
The simplest way to look at it is=A0 Session B was lock out when the D= rop table command was issued from Session A.=A0 Now when session B finally = got its chance to drop/delete the table it was already gone .
=A0
What kind error were you expecting from Postgresql to Return when it c= an't find the table???
=A0
In the future please=A0 don't cross post to multiple lists. =A0
=A0
---- Message from raghavendra t <raagavendra.rao@gmail.com> at 04-03-20= 10 10:08:11 PM ------
=A0
step 6 - Issue the commit in Session A
=A0
postgres=3D# commit;
=A0
Step -7 now=A0we can the see the error in the session B
=A0
ERROR: cache lookup failed for relation X
Could plese tell me, why this is generated and what is the cause.
=A0
=A0
Thanks in advance
=A0
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.
=A0
CONFIDENTIALITY NOTICE: This e-mail, including attachments, may contai= n legally privileged, confidential or other information proprietary to Magw= erks Corporation and is intended solely for the use of the individual to wh= om 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 v= iewing, dissemination, distribution or copying of this e-mail is strictly p= rohibited. If you have received this e-mail in error, please notify the sen= der by replying to this message and destroy all occurrences of this e-mail = immediately.
Thank you.
=A0
=A0
--001636b2b030e868270483604b24--