Re: Index-only-scans, indexam API changes - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Index-only-scans, indexam API changes
Date
Msg-id 407d949e0907130202s33124d3drea41fb66dddd2ea6@mail.gmail.com
Whole thread Raw
In response to Index-only-scans, indexam API changes  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Mon, Jul 13, 2009 at 8:19 AM, Heikki
Linnakangas<heikki.linnakangas@enterprisedb.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?

-- 
greg
http://mit.edu/~gsstark/resume.pdf


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Index-only-scans, indexam API changes
Next
From: Peter Eisentraut
Date:
Subject: Re: [pgsql-www] Launching commitfest.postgresql.org