Re: Updated bitmap index patch

From: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
To: Gavin Sherry <swm(at)alcove(dot)com(dot)au>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Updated bitmap index patch
Date: 2007-05-03 04:56:59
Message-ID: 46396B9B.1090007@paradise.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Gavin Sherry wrote:
> Hi all,
>
> Attached is an updated bitmap index patch. It contains bug fixes, API
> changes, binary changes (page identifier to distinguish it from other
> indexes) and has been brought up to HEAD.
>

I have applied this to todays HEAD performed some quick tests - looks
good! I have to re-create a TPC-H dataset to test one of the previous
bugs, so I'll probably look at that tomorrow or so.

> I worked on a few approaches to VACUUM, none very satisfactory. The
> problem is, breaking a compressed word representing matches can have
> serious consequences -- at the least, creation of new words, at the worst,
> creation of a new page. If a lot of this were to happen, REINDEX would be
> much more efficient (this is what earlier patches did).
>
> One approach I looked at was modifying the existing read API to be able to
> do something like "kill prior tuple". This, I think, made the API quite
> complex and it was hard to implement, since the existing mechanism
> decompresses words on the fly and it would be hard to identify which TID
> is no longer a match. So, I dropped this idea pretty quickly.
>
> The second approach is to just manually traverse each vector and change
> matches to non-matches where necessary. The complexity then is in managing
> the consequences of breaking compressed words, doing WAL (efficiently) and
> calculating free space. I've only partially implemented this approach. At
> this stage, I don't have time to finish it due to other commitments.
>

The second approach seems like better the way to go (as far as I
understand the issues...). How much work is remaining on this? - not
sure that I'll have time to look at it either ... but may as well know
the size to the job :-) !

Cheers

Mark

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-05-03 05:24:45 Re: CREATE TABLE LIKE INCLUDING INDEXES support
Previous Message Gavin Sherry 2007-05-03 03:51:29 Updated bitmap index patch

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-05-03 05:24:45 Re: CREATE TABLE LIKE INCLUDING INDEXES support
Previous Message Gavin Sherry 2007-05-03 03:51:29 Updated bitmap index patch