Re: Problem with bitmap-index-scan plan - Mailing list pgsql-performance

From Tom Lane
Subject Re: Problem with bitmap-index-scan plan
Date
Msg-id 21981.1152829978@sss.pgh.pa.us
Whole thread Raw
In response to Problem with bitmap-index-scan plan  (jkapad@csd.uoc.gr)
Responses Re: Problem with bitmap-index-scan plan  (Kapadaidakis Yannis <jkapad@csd.uoc.gr>)
List pgsql-performance
jkapad@csd.uoc.gr writes:
> ... is quite reasonable.The table has 1.000.000 rows (17.242 pages). From
> pg_stat_get_blocks_fetched I can see that there were 102 page requests for
> table. So all things seem to work great here!

> But if I multiply the size of the table ten-times (10.000.000 rows - 172.414
> pages) and run the same query I get:
> ...
> which is slower even than a seq scan. Now I get that there were 131.398 page
> requests for table in order to retrieve almost 1250 tuples!Can someone explain
> why this is happening? All memory parameters are set to default.

You probably need to increase work_mem so that the bitmaps don't become
lossy ...

            regards, tom lane

pgsql-performance by date:

Previous
From: "Medora Schauer"
Date:
Subject: Re: hyper slow after upgrade to 8.1.4
Next
From: Mark Kirkwood
Date:
Subject: Re: Kill a session