Re: index & Bitmap Heap Scan - Mailing list pgsql-performance

From Tom Lane
Subject Re: index & Bitmap Heap Scan
Date
Msg-id 29055.1188320158@sss.pgh.pa.us
Whole thread Raw
In response to index & Bitmap Heap Scan  (Paul <paul@wayr.org>)
Responses Re: index & Bitmap Heap Scan  (Paul <paul@wayr.org>)
List pgsql-performance
Paul <paul@wayr.org> writes:
> Why in the first case, pgsql uses the "better" index and if i search
> r_service instead of r_numero pgsql does a "Bitmap Heap scan" first ?

Given the difference in the number of rows to be fetched, both plan
choices look pretty reasonable to me.  If you want to experiment,
you can try forcing the other choice in each case (use enable_indexscan
and enable_bitmapscan) and see how fast it is, but I suspect the planner
got it right.

Beware of cache effects when trying two plans in quick succession ---
the second one might go faster just because all the data is already
swapped in.

            regards, tom lane

pgsql-performance by date:

Previous
From: Mark Lewis
Date:
Subject: Re: Fwd: 8.2 Query 10 times slower than 8.1 (view-heavy)
Next
From: "Anton Melser"
Date:
Subject: Re: Postgres performance problem