From: | Gavin Sherry <swm(at)alcove(dot)com(dot)au> |
---|---|
To: | pgsql-patches(at)postgresql(dot)org |
Subject: | Updated bitmap index patch |
Date: | 2007-03-12 13:06:21 |
Message-ID: | Pine.LNX.4.58.0703130002080.21774@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Hi all,
I've updated the bitmap index patch. It can be found here:
http://www.alcove.com.au/~swm/bitmap-2007-03-12.diff
This fixes some bugs introduced in the last patch, catches up to HEAD and
tidies up the executor code. I want to do a little more tidying, such as
reverting the name changes we made. multiscan still sounds alright.
I've been thinking about vacuum as well. Something along the lines of what
Heikki mentioned earlier -- namely, the ability to iterate the bitmap
setbit by setbit is in order. What I have in mind, though, is that when we
find a reaped setbit, we mark the position and continue to iterate until
we find a non reaped setbit. When, we update the underlying bitmap vector
to reflect the non-set bits.
Thoughts?
Thanks,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2007-03-12 13:35:24 | Re: Updated bitmap index patch |
Previous Message | Heikki Linnakangas | 2007-03-12 12:25:18 | Bitmapscan changes |