Luke Lonergan wrote:
> Bruce,
>
> We have a bitmap index AM in Bizgres (on PG 8.1.3) that is functional and
> achieves very worthwhile (10x+) performance and space objectives.
>
> It is a large patch, and introduces the access method along with modifying
> the appropriate executor nodes. The lat
Bruce,
We have a bitmap index AM in Bizgres (on PG 8.1.3) that is functional and
achieves very worthwhile (10x+) performance and space objectives.
It is a large patch, and introduces the access method along with modifying
the appropriate executor nodes. The latter part was necessary because of
t
Victor Yegorov wrote:
> Hi again.
>
> Here's an updated patch, that fixes several bugs and is synced with HEAD.
Are you closer to submitting this patch for application?
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDBhttp://www.enterprisedb.com
+ If your life is a hard drive,
This has been saved for the 8.2 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Victor Yegorov wrote:
> Hi again.
>
> Here's an updated patch, that fixes several bugs and is synced with HEAD.
>
>
Hi again.
Here's an updated patch, that fixes several bugs and is synced with HEAD.
--
Victor Y. Yegorov
diff-20050727-2.gz
Description: Binary data
---(end of broadcast)---
TIP 6: explain analyze is your friend
I've managed to fix all bugs I've met so far.
Attached is an updated patch.
Comments:
o README should be updated to reflect the changes I've done recently;
o I'm still haven't tested ammarkpos and amrestrpos functions --- planner is
choosing Nested Loop all the time and my knowledge of query
Hello.
I've been working on bitmap index AM for some time.
The situation is --- in general it works, but there're some problems I cannot
fix myself. I've been using Teodor's scripts for concurrency tests (modified a
bit), unfortunately without success.
Anyway, here's the patch. I hope someone wi
