Re: Index AM change proposals, redux - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Index AM change proposals, redux
Date
Msg-id 24934.1207866632@sss.pgh.pa.us
Whole thread Raw
In response to Re: Index AM change proposals, redux  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: Index AM change proposals, redux  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
Heikki Linnakangas <heikki@enterprisedb.com> writes:
> Tom Lane wrote:
>> Heikki Linnakangas <heikki@enterprisedb.com> writes:
>>> Note that we'll need to add candidate match support to the regular index 
>>> scan API as well for that.
>> 
>> [ confused... ]  Thought you'd done that in this patch?

> No, I only modified the bitmap scan API.

Okay.  I applied what you'd done (with minor revisions), but we'll have
to fix up the regular indexscan API before anything can be done about
@@@.  I'll take a look at that part tomorrow.

Teodor, do you have any thoughts about exactly how you'd fix @@@ ?
I suppose that the recheck-need is not really a property of specific
tuples, but of a particular query, for that case.  Where would you
want to detect that?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Commit fest queue
Next
From: Andrew Dunstan
Date:
Subject: Re: Commit fest queue