Guillaume Cottenceau wrote: > If I'm correct, you're basically telling postgresql that your > disk is unusually fast compared to your CPU. Even if some queries > will run faster from a side-effect of these settings, you're > likely to create other random problems... If this is set globally and the active portion of the database is not highly cached, yes. If the example query is typical of the level of caching for frequently-run queries, it might provide an overall performance boost to set these in postgresql.conf. The original problem was that the optimizer was grossly over-estimating the cost of returning a tuple through the index, which was taking about 0.01 ms per tuple. -Kevin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
