Re: ERROR: cache lookup failed for relation 17442 (repost)

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Guerin <guerin(at)rentec(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: ERROR: cache lookup failed for relation 17442 (repost)
Date: 2005-02-07 22:29:41
Message-ID: 20050207222941.GA30539@dcc.uchile.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Feb 07, 2005 at 05:07:47PM -0500, Tom Lane wrote:

> A more general issue is that we now have a pile of "catalog inquiry"
> functions that all make use of backend internal lookups and therefore
> reflect SnapshotNow behavior to the user. This has bothered me for
> some
> time,

Can we pass a Snapshot as a parameter to the internal lookups? Or set a
global variable to indicate this is not really a internal lookup, and
reset it afterwards?

--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"The problem with the future is that it keeps turning into the present"
(Hobbes)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2005-02-07 22:34:49 Re: ERROR: cache lookup failed for relation 17442 (repost)
Previous Message Hans-Jürgen Schönig 2005-02-07 22:13:36 Re: ERROR: cache lookup failed for relation 17442 (repost)