From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Scan by TID (was RE: [HACKERS] How to add a new build-in operator) |
Date: | 1999-10-11 19:14:16 |
Message-ID: | 199910111914.PAA00307@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> > Yes,I have done a part of my story.
> > I would add new type of path and scan by which we are able to access
> > tids directly.
>
> Yes, new path type, new plan type, probably a new access method if
> you want to keep things clean in the executor, cost-estimation routines
> in the planner, etc. etc.
>
> Looks like a lot of work, and a lot of added code bulk that will
> have to be maintained. I haven't figured out why you think it's
> worth it... tids are so transient that I don't see much need for
> finding tuples by them...
That's why I just suggested a more short-circuited option of snatching
tid oids from expressions, and doing a heap_fetch directly at that point
to avoid the index scan. Seems it could be done in just one file.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-10-11 19:15:26 | Re: Scan by TID (was RE: [HACKERS] How to add a new build-in operator) |
Previous Message | Bruce Momjian | 1999-10-11 19:10:57 | Re: Scan by TID (was RE: [HACKERS] How to add a new build-in operator)] |