| From: | Sailesh Krishnamurthy <sailesh(at)cs(dot)berkeley(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: proposal: be smarter about i/o patterns in index scan |
| Date: | 2004-05-19 16:23:33 |
| Message-ID: | mjq7jv8jshm.fsf@cs.berkeley.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
Tom> For starters, read the previous discussions of this in the
Tom> archives.
Tom> Two questions you should have answers to before starting to
Tom> implement, rather than after, are how to deal with locking
Tom> considerations and what will be the implications of giving up
Tom> the property that indexscans deliver sorted output.
I don't know about the former, but as to the latter, we should
certainly have the ability for both output sorted by key and
TID-List-Fetch ...
--
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-05-19 16:43:52 | Re: Call for 7.5 feature completion |
| Previous Message | Tom Lane | 2004-05-19 16:10:54 | Re: Call for 7.5 feature completion |