Re: Using Bitmap scan instead of Seq scan

You cannot ALWAYS do an indexed scan - sometimes the only option for the
parser is to do a sequential scan (thus you can say "avoid unless you have
to" but you can never truly disable sequential scanning).

Given limited knowledge of full-text searching I cannot explain why this
specific query is unable (or unwilling) to use an index. Since you have not
provided any index options for the list to consider we may even assume you
have NO indexes and thus none to choose from...

I'd suggest looking at chapters 11 (Indexes) and 12 (Full-Text) of the
documentation while awaiting further responses from the list (after you
describe what indexes you have already defined on relevant tables - and
maybe provide the raw query as well).

David J

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Ahmed Ossama
Sent: Monday, February 14, 2011 12:40 PM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] Using Bitmap scan instead of Seq scan

I did a REINDEX and ANALYZE on the table, disabled the seqscan and ran the
query again with the same result.

My question how do I make PostgreSQL always uses bitmap scan instead of seq
scan?

Any advice is very much appreciated.

Best Regards,
Ahmed Ossama

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