| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index-only-scans, indexam API changes |
| Date: | 2009-07-13 09:02:45 |
| Message-ID: | 407d949e0907130202s33124d3drea41fb66dddd2ea6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 13, 2009 at 8:19 AM, Heikki
Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>
> I propose that we split index_getnext into two steps: fetching the next
> match from the index (index_next()), and fetching the corresponding heap
> tuple (index_fetch()).
A pretty trivial concern, but it seems confusing that the function to
fetch a tuple from the heap is called "index_fetch()"... Perhaps
something more explicit like index_fetch_heap_tuple() would be
clearer?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-07-13 12:47:22 | Re: Launching commitfest.postgresql.org |
| Previous Message | Heikki Linnakangas | 2009-07-13 07:19:02 | Index-only-scans, indexam API changes |