Re: cost_nonsequential_access() - Mailing list pgsql-patches

From Tom Lane
Subject Re: cost_nonsequential_access()
Date
Msg-id 1788.1086707623@sss.pgh.pa.us
Whole thread Raw
In response to cost_nonsequential_access()  (Manfred Koizar <mkoi-pg@aon.at>)
Responses Re: cost_nonsequential_access()  (Manfred Koizar <mkoi-pg@aon.at>)
List pgsql-patches
Manfred Koizar <mkoi-pg@aon.at> writes:
> The comment describing cost_nonsequential_access() says that the two
> functions "meet in the middle".  They meet at random_page_cost/2,
> however, not in the middle between 1 and random_page_cost.  For
> random_page_cost < 2 the result can be less than 1 for relpages near
> effective_cache_size.  I don't think that this was intended.

You're right, I failed to consider that random_page_cost might be less
than 2.

> This patch makes sure that cost_nonsequential_access() is always between
> 1 and randon_page_cost and the functions meet a (1+random_page_cost)/2.

This patch seems to do considerably more violence to the equations than
is needed to cover that oversight, though.  The old behavior was
intentionally nonlinear in relsize; this is not.

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: fix schema ownership for database owner on first connection
Next
From: Fabien COELHO
Date:
Subject: Re: fix schema ownership for database owner on first