Marc Cousin <cousinmarc(at)gmail(dot)com> wrote:
> the hot parts of these 2 tables are extremely likely to be in the
> database or linux cache (buffer hit rate was 97% in the example
> provided). Moreover, the first two queries of the insert procedure
> fill the cache for us...
This would be why the optimizer does the best job estimating the
relative costs of various plans when you set the random_page_cost and
seq_page_cost very low.
-Kevin