Gavin Sherry wrote:
> o Improving VACUUM support -- currently, VACUUM FULL means REINDEX for
> bitmaps. Heikki Linnakangas offered to work on this. Heikki, are you
> still interested?

BTW vacuuming seems quite broken as it is:

hlinnaka@heikkilaptop:~/pgsql.bitmap$ ~/pgsql.bitmap/bin/psql -a
postgres < vacuumtest.sql
drop table if exists test;
DROP TABLE
create table test (key int);
CREATE TABLE
create index test_bm on test using bitmap (key);
CREATE INDEX
insert into test values (1);
INSERT 0 1
delete from test;
DELETE 1
vacuum test;
VACUUM
insert into test values (2);
INSERT 0 1
select * from test where key = 1;
key
-----
2
(1 row)

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

On Tue, 5 Dec 2006, Heikki Linnakangas wrote:

> Gavin Sherry wrote:
> > o Improving VACUUM support -- currently, VACUUM FULL means REINDEX for
> > bitmaps. Heikki Linnakangas offered to work on this. Heikki, are you
> > still interested?
>
> BTW vacuuming seems quite broken as it is:
>
> hlinnaka@heikkilaptop:~/pgsql.bitmap$ ~/pgsql.bitmap/bin/psql -a
> postgres < vacuumtest.sql
> drop table if exists test;
> DROP TABLE
> create table test (key int);
> CREATE TABLE
> create index test_bm on test using bitmap (key);
> CREATE INDEX
> insert into test values (1);
> INSERT 0 1
> delete from test;
> DELETE 1
> vacuum test;
> VACUUM
> insert into test values (2);
> INSERT 0 1
> select * from test where key = 1;
> key
> -----
> 2
> (1 row)

Oops :-).

Thanks for pointing it out. I think I might have busted something merging
with HEAD. Don't you hate that?

Thanks,

Gavin

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster