Re: Performance With Joins on Large Tables - Mailing list pgsql-performance

From Jeff Davis
Subject Re: Performance With Joins on Large Tables
Date
Msg-id 1158163655.29889.57.camel@dogma.v10.wvs
Whole thread Raw
In response to Re: Performance With Joins on Large Tables  ("Joshua Marsh" <icub3d@gmail.com>)
Responses Re: Performance With Joins on Large Tables  ("Joshua Marsh" <icub3d@gmail.com>)
List pgsql-performance
On Wed, 2006-09-13 at 08:49 -0600, Joshua Marsh wrote:
> That seems to have done it.  Are there any side effects to this
> change?  I read about random_page_cost in the documentation and it
> seems like this is strictly for planning.  All the tables on this
> database will be indexed and of a size similar to these two, so I
> don't see it  causing any other problems.  Though I would check though
> :)
>

Right, it's just used for planning. Avoid setting it too low, if it's
below about 2.0 you would most likely see some very strange plans.
Certainly it doesn't make sense at all to set it below 1.0, since that
is saying it's cheaper to get a random page than a sequential one.

What was your original random_page_cost, and what is the new value you
set it to?

Regards,
    Jeff Davis




pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: sql-bench
Next
From: "Joshua Marsh"
Date:
Subject: Re: Performance With Joins on Large Tables