From: | "Victor Y(dot) Yegorov" <viy(at)mits(dot)lv> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Implementing Bitmap Indexes |
Date: | 2005-01-29 17:39:01 |
Message-ID: | 20050129173901.GA8056@mits.lv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [29.01.2005 18:24]:
> "Victor Y. Yegorov" <viy(at)mits(dot)lv> writes:
> > I remember, Tom Lane suggested on-disk bitmaps
>
> I have suggested no such thing, and in fact believe that the sort of
> index structure you are proposing would be of very little use.
Why? I thought they would be useful for data warehouse databases.
Maybe I said something "the wrong way", but what I'm trying to implement
is exactly what is said about in the first link you've posted below:
http://archives.postgresql.org/pgsql-hackers/2004-10/msg00439.php
Or am I misunderstanding the point?
> What I've been hoping to look into is *in memory* bitmaps used as an
> interface between index scans and the subsequent heap lookups.
Sorry, that was what I've been speaking of.
Anyway, bitmap indexes API could be used for in-memory bitmaps you're speaking
of.
--
Victor Y. Yegorov
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Y. Yegorov | 2005-01-29 17:41:20 | Re: Implementing Bitmap Indexes |
Previous Message | Tom Lane | 2005-01-29 16:33:09 | Re: [pgsql-hackers] Patent issues and 8.1 |