pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Sabino Mullane <greg@turnstep.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Changing the random_page_cost default (was: cpu_tuple_cost)
Date: Tue, 15 Mar 2005 10:22:56 -0500
Message-ID: <6320.1110900176@sss.pgh.pa.us> (raw)
In-Reply-To: <d1376f1e9679b10ba7a9d8cac343ee05@biglumber.com>
References: <d1376f1e9679b10ba7a9d8cac343ee05@biglumber.com>

"Greg Sabino Mullane" <greg@turnstep.com> writes:
> N.B. My own personal starting default is 2, but I thought 3 was a nice
> middle ground more likely to reach consensus here. :)

Your argument seems to be "this produces nice results for me", not
"I have done experiments to measure the actual value of the parameter
and it is X".  I *have* done experiments of that sort, which is where
the default of 4 came from.  I remain of the opinion that reducing
random_page_cost is a band-aid that compensates (but only partially)
for problems elsewhere.  We can see that it's not a real fix from
the not-infrequent report that people have to reduce random_page_cost
below 1.0 to get results anywhere near local reality.  That doesn't say
that the parameter value is wrong, it says that the model it's feeding
into is wrong.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <6320.1110900176@sss.pgh.pa.us>
Permalink:  ../6320.1110900176@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6320.1110900176@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, greg@turnstep.com
  Subject: Re: Changing the random_page_cost default (was: cpu_tuple_cost)
  In-Reply-To: <6320.1110900176@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox