Thread: Default cost variables in postgresql.conf

Hi:

  Are the "cost" variables (e.g.
random_page_cost,cpu_tuple_cost,cpu_index_tuple_cost)
in postgresql.conf optimal for a particular set of
platform / hardware requirements? (i.e. the configs
works best for let say if you have PIII computer w/
IDE as storage).

   I'm asking this since a lot of softwares' configs
are defaulted to a "conservative" settings where
allowances are given for people who have older/slower
CPUs(w/ not so large amount of memory).


   Thank you in advance.

ludwig.

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

On Mon, Oct 21, 2002 at 12:04:58AM -0700, Ludwig Lim wrote:
> Hi:
>
>   Are the "cost" variables (e.g.
> random_page_cost,cpu_tuple_cost,cpu_index_tuple_cost)
> in postgresql.conf optimal for a particular set of
> platform / hardware requirements? (i.e. the configs

Not exactly.  They're best guesses.  If you check the admin guide,
you'll see that there's a note about these which says that there is
not a well-defined method for calculating these things, so you are
encouraged to experiment and share your findings.  They _are_ known
to be conservative defaults, like everything else in the system.

A

--
----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8
                                         +1 416 646 3304 x110