Re: [PATCHES] WIP: bitmap indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jie Zhang" <jzhang(at)greenplum(dot)com>
Cc: "Gavin Sherry" <swm(at)linuxworld(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] WIP: bitmap indexes
Date: 2006-08-17 12:54:00
Message-ID: 5097.1155819240@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"Jie Zhang" <jzhang(at)greenplum(dot)com> writes:
> This sounds great. One thing I am concern about is that this will add the
> dependency of node types into the access methods. If we still keep
> nodeBitmapIndexscan and let it do the bitmap construction for tids returned
> by amgetmulti.

No, I'm assuming the other proposal that was on the table, namely to get
rid of amgetmulti in its current form and instead have an AM call that
delivers a bitmap in one step. (Probably should rename the pg_am column
to something like amgetbitmap.) nodeBitmapIndexscan would become pretty
trivial. For the existing AMs this just means that they call
tbm_add_tuple(s) for themselves, which is no big problem, especially
considering that they probably get to save some code by not having to
stop the indexscan when the buffer array gets full.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-08-17 13:02:36 Re: Going for "all green" buildfarm results
Previous Message Andrew Dunstan 2006-08-17 12:52:42 Re: Enum proposal / design

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-08-17 13:14:57 Re: CREATE INDEX ... ONLINE
Previous Message Martijn van Oosterhout 2006-08-17 12:23:48 Re: pgstattuple extension for indexes