| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| 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:34:49 |
| Message-ID: | 497.1107815689@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> 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.
> 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?
The first seems awfully messy, and the second awfully dangerous.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Guerin | 2005-02-07 22:42:35 | Re: ERROR: cache lookup failed for relation 17442 (repost) |
| Previous Message | Alvaro Herrera | 2005-02-07 22:29:41 | Re: ERROR: cache lookup failed for relation 17442 (repost) |