Re: Indexam interface proposal

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Indexam interface proposal
Date: 2007-03-19 13:11:15
Message-ID: 45FE8BF3.8010901@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Martijn van Oosterhout wrote:
> On Mon, Mar 19, 2007 at 12:23:01PM +0000, Heikki Linnakangas wrote:
>> Currently amgettuple returns one matching tuple at a time, in index
>> order. I'm proposing two changes to add support for
>> - candidate matches
>
> IIRC indexes can already ask to have the system recheck conditions on
> returned tuples. For example GiST can return more tuples than actually
> match. That's what the amopreqcheck column is for in pg_amop.

Right, except that flag is per operator in operator class, and what I'm
proposing is that the index could pass a flag per tuple in the scan.
Some tuples in the scan might need rechecking, some might not. The need
for rechecking in clustered indexes is orthogonal to the need arising
from the lossyness of GiST operators.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2007-03-19 13:17:24 Re: Buildfarm feature request: some way to track/classify failures
Previous Message Gregory Stark 2007-03-19 13:04:03 Re: Buildfarm feature request: some way to track/classify failures