Skip site navigation (1) Skip section navigation (2)

Updated bitmap index patch

From: Gavin Sherry <swm(at)alcove(dot)com(dot)au>
To: pgsql-patches(at)postgresql(dot)org
Subject: Updated bitmap index patch
Date: 2007-05-03 03:51:29
Message-ID: Pine.LNX.4.58.0705031335240.10105@linuxworld.com.au (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
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 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.

Thanks,

Gavin

Attachment: bitmap-2007-05-03.diff.gz
Description: application/x-gzip (82.7 KB)

Responses

pgsql-hackers by date

Next:From: Mark KirkwoodDate: 2007-05-03 04:56:59
Subject: Re: Updated bitmap index patch
Previous:From: Jeff DavisDate: 2007-05-03 00:24:18
Subject: Re: Sequential scans

pgsql-patches by date

Next:From: Mark KirkwoodDate: 2007-05-03 04:56:59
Subject: Re: Updated bitmap index patch
Previous:From: Tom LaneDate: 2007-05-02 21:25:39
Subject: Re: Clear up strxfrm() in UTF-8 with locale on Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group