Re: cpu_tuple_cost - Mailing list pgsql-performance

From Bruce Momjian
Subject Re: cpu_tuple_cost
Date
Msg-id 200503150217.j2F2HqA01460@candle.pha.pa.us
Whole thread Raw
In response to Re: cpu_tuple_cost  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-performance
Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > Reducing random_page_cost is usually the best way to get the
> > planner to favor indexscans more.
>
> On that note, can I raise the idea again of dropping the default
> value for random_page_cost in postgresql.conf? I think 4 is too
> conservative in this day and age. Certainly the person who will
> be negatively impacted by a default drop of 4 to 3 will be the
> exception and not the rule.

Agreed.  I think we should reduce it at least to 3.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-performance by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Re: cpu_tuple_cost
Next
From: Tom Lane
Date:
Subject: Re: cpu_tuple_cost