On Mon, Feb 14, 2011 at 12:40 PM, Ahmed Ossama wrote:
> 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.
>
Jon Nelson writes:
> Does this suggest that the config items "disable_seqscan" (and friends)
> should be renamed to "avoid_seqscan" ?
Some of them actually are disable, some are only avoid. The
documentation says which is which, but I don't think creating a
distinction at the naming level would
On Mon, Feb 14, 2011 at 11:57 AM, David Johnston wrote:
> 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).
>
Does this suggest that the
ma
Sent: Monday, February 14, 2011 12:40 PM
To: pgsql-general@postgresql.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
Greetings guys,
I am running PostgreSQL 8.4, my database is 60GB. My problem is that
there are some queries run extremely fast (when bitmap scan is used),
while others take more than 600secs to respond (when seq scan is used).
Here is a sample of the queries which uses seq scan...
[2011-02-1
