Re: Index usage when bitwise operator is used - Mailing list pgsql-performance

From valgog
Subject Re: Index usage when bitwise operator is used
Date
Msg-id 1190111783.077030.48670@22g2000hsm.googlegroups.com
Whole thread Raw
In response to Re: Index usage when bitwise operator is used  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Hi Tom,

do you think it would be a good idea to ask GIN index team to
implement an int-based bitmap set indexing operator for GIN/GiST based
indexes? Or there will be a possibility to somehow optimally index
arrays of enumerations to implement such bitmap structures in 8.3 or
later postgresql versions?

With best regards,

-- Valentine

On Sep 17, 3:37 pm, t...@sss.pgh.pa.us (Tom Lane) wrote:
> "Kevin Grittner" <Kevin.Gritt...@wicourts.gov> writes:
> > On Mon, Sep 17, 2007 at  2:49 AM, in message
> > <1190015368.148293.56...@y42g2000hsy.googlegroups.com>, valgog
> > <val...@gmail.com> wrote:=20
> >> Are you sure you understood what was the question?
>
> >> Is the TBL1.CATEGORY = TBL2.CATEGORY the same as TBL1.CATEGORY &
> >> TBL2.CATEGORY > 0?
> > Yes, given that he stipulated that one and only one bit would be set.
>
> Really?  In that case, isn't this bit-field just a bad implementation of
> an enum-style field?
>
>                         regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majord...@postgresql.org so that your
>        message can get through to the mailing list cleanly



pgsql-performance by date:

Previous
From: "Galantucci Giovanni"
Date:
Subject: R: DELETE queries slow down
Next
From: Tom Lane
Date:
Subject: Re: Query works when kludged, but would prefer "best practice" solution