Gavin Sherry wrote:
> On Wed, 18 Oct 2006, Heikki Linnakangas wrote:
>
> > Hi,
> >
> > I don't want to harass you :), but what's the status with the bitmap
> > index code? Is there something I can do to help?
> >
>
> Hi Heikki,
>
> The streaming is implemented, as are range queries. I need to br
On Wed, 18 Oct 2006, Heikki Linnakangas wrote:
> Hi,
>
> I don't want to harass you :), but what's the status with the bitmap
> index code? Is there something I can do to help?
>
Hi Heikki,
The streaming is implemented, as are range queries. I need to bring it up
to HEAD and back-patch to bizgre
On 10/18/06 2:41 AM, "Heikki Linnakangas" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I don't want to harass you :), but what's the status with the bitmap
> index code? Is there something I can do to help?
Not at all. We will send you the new patch soon. Your comments are most
appreciated.
Thanks,
Ji
Hi,
I don't want to harass you :), but what's the status with the bitmap
index code? Is there something I can do to help?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0,
Luke Lonergan wrote:
Mark,
On 9/25/06 11:32 AM, "Mark Wong" <[EMAIL PROTECTED]> wrote:
Yeah, basically gather as many stats as I can to accurately profile the
overall system performance. I thought it would be appropriate to use a
TPC-H based workload as one measuring stick to use for bitmap i
On Tue, 26 Sep 2006, Heikki Linnakangas wrote:
> Looks a bit better now, though I think you need to think more about the
> encapsulation of the structs. More detailed comments below.
>
> Jie Zhang wrote:
> > Essentially, we want to have a stream bitmap object that has an iterator,
> > which will b
Looks a bit better now, though I think you need to think more about the
encapsulation of the structs. More detailed comments below.
Jie Zhang wrote:
Essentially, we want to have a stream bitmap object that has an iterator,
which will be able to iterate through the bitmaps. The BitmapIndexscan,
Mark,
On 9/25/06 11:32 AM, "Mark Wong" <[EMAIL PROTECTED]> wrote:
> Yeah, basically gather as many stats as I can to accurately profile the
> overall system performance. I thought it would be appropriate to use a
> TPC-H based workload as one measuring stick to use for bitmap indexes.
Note that
Hi Jie,
Yeah, basically gather as many stats as I can to accurately profile the
overall system performance. I thought it would be appropriate to use a
TPC-H based workload as one measuring stick to use for bitmap indexes.
Mark
Jie Zhang wrote:
Hi Mark,
Thanks for doing the test. I checked
Hi Mark,
Thanks for doing the test. I checked out the link you provided below. I am a
little confused about the goal of these tests. Do you plan to test the
overall performance of postgreSQL on handling TPC-H queries?
Thanks,
Jie
On 9/22/06 3:45 PM, "Mark Wong" <[EMAIL PROTECTED]> wrote:
> Jie
Gavin & Heikki,
>>
>> The handling of stream and hash bitmaps looks pretty complicated to me.
>> All the bitmap-related nodes have logic to handle both types slightly
>> differently. It all seems to come down to that if a subnode (or
>> amgetbitmap in a bitmap index scan node) returns a StreamBit
Jie Zhang wrote:
Hi Heikki and all,
I just sent the latest bitmap index patch to the list. I am not sure if
there is any size limit for this mailing list. If you have received my
previous email, please let me know.
Hi Jie,
I know I said I was going to get testing on this months ago but I've
On 9/19/06 5:15 AM, "Gavin Sherry" <[EMAIL PROTECTED]> wrote:
> On Tue, 19 Sep 2006, Heikki Linnakangas wrote:
>
>> Jie Zhang wrote:
>>> Hi Heikki and all,
>>>
>>> Please find the latest bitmap index patch in the attachment. This patch is
>>> generated against the postgresql cvs head.
>>>
>>
On Tue, 19 Sep 2006, Heikki Linnakangas wrote:
> Jie Zhang wrote:
> > Hi Heikki and all,
> >
> > Please find the latest bitmap index patch in the attachment. This patch is
> > generated against the postgresql cvs head.
> >
>
> Thanks.
>
> The handling of stream and hash bitmaps looks pretty compli
Jie Zhang wrote:
Hi Heikki and all,
Please find the latest bitmap index patch in the attachment. This patch is
generated against the postgresql cvs head.
Thanks.
The handling of stream and hash bitmaps looks pretty complicated to me.
All the bitmap-related nodes have logic to handle both
Hi Heikki and all,
I just sent the latest bitmap index patch to the list. I am not sure if
there is any size limit for this mailing list. If you have received my
previous email, please let me know.
Thanks,
Jie
On 9/12/06 2:43 AM, "Heikki Linnakangas" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What's
Hi Heikki,
Gavin and I are trying to merge our changes together this week. We will post
a new patch by the end of this week. This patch will include some style
fixes, bug fixes, and the stream bitmap implementation.
I will look into the problems you have mentioned in this email. Yes, vacuum
curre
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> What's the status of the bitmap index patch? Have you worked on it since
> the last posted patch
> (http://archives.postgresql.org/pgsql-patches/2006-08/msg3.php)?
Gavin and Jie have made major changes since that version (or at least
they'd be
Hi,
What's the status of the bitmap index patch? Have you worked on it since
the last posted patch
(http://archives.postgresql.org/pgsql-patches/2006-08/msg3.php)?
I've started to review it, to get it into CVS early in the 8.3 cycle. I
just want to make sure that I'm working on the lates
19 matches
Mail list logo
