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

From Kevin Grittner
Subject Re: Index usage when bitwise operator is used
Date
Msg-id 46ED7CCD.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Index usage when bitwise operator is used  ("W.Alphonse HAROUNY" <wharouny@gmail.com>)
Responses Re: Index usage when bitwise operator is used  (valgog <valgog@gmail.com>)
List pgsql-performance
>>> On Thu, Sep 13, 2007 at  7:30 AM, in message
<f97d4e240709130530ve3cc522g61ccca23335618f4@mail.gmail.com>, "W.Alphonse
HAROUNY" <wharouny@gmail.com> wrote:

>    and each binary value of [variableCategory] may only hold a single binary
> '1'.

>  TBL1.CATEGORY & TBL2.CATEGORY <> 0  //-- where & is the AND bitwise
> operator

What about saying?:

  TBL1.CATEGORY = TBL2.CATEGORY

If your indexes include this and the other columns which cause the tables
to be related, one or both of them stand a pretty good chance of evaluating
to the lowest-cost method to join the tables.  Forcing a query to use an
index outside of it being the cheapest path is rarely productive.

-Kevin


pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1
Next
From: valgog
Date:
Subject: Re: Index usage when bitwise operator is used