Search Postgresql Archives

Re: forcing use of more indexes (bitmap AND)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 14, 2008 at 12:28 AM, Ow Mun Heng <Ow.Mun.Heng@xxxxxxx> wrote:
> 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

Would setting enable_bitmapscan=off do that?  I'm not being sarcastic,
I really don't know.

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux