forcing use of more indexes (bitmap AND) - Mailing list pgsql-general

From Ow Mun Heng
Subject forcing use of more indexes (bitmap AND)
Date
Msg-id 1205476095.354.29.camel@neuromancer.home.net
Whole thread Raw
Responses Re: forcing use of more indexes (bitmap AND)  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Re: forcing use of more indexes (bitmap AND)  ("A. Kretschmer" <andreas.kretschmer@schollglas.com>)
List pgsql-general
query is something like this

    Select *
    from v_test
    where acode Like 'PC%'
    and rev = '0Q'
    and hcm = '1'
    and mcm = 'K'

where acode, rev, hcm, mcm are all indexes.

Currently this query is only using the rev and mcm for the bitmapAND.
it then does a bitmap heap scan using the acode and the hcm indexes.

I would like to try to see if forcing the planner to favour heavier usage of the indexes would yield faster results.

I've tried lowering random_page_cost(default 4) down to 2 with no change in planner.


pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Can't rename an existnig DB because it doesn't exist???
Next
From: Oleg Bartunov
Date:
Subject: Re: tsearch2 word separators