pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Hoffmann <jeff@propertykey.com>
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 07:31:19 -0600
Message-ID: <8dd8c52718f9c9153fe089d64a496150@propertykey.com> (raw)
In-Reply-To: <d1376f1e9679b10ba7a9d8cac343ee05@biglumber.com>
References: <d1376f1e9679b10ba7a9d8cac343ee05@biglumber.com>


On Mar 15, 2005, at 6:35 AM, Greg Sabino Mullane wrote:

> Granted, I don't work on
> any huge, complex, hundreds of gig databases, but that supports my 
> point -
> if you are really better off with a /higher/ (than 3) 
> random_page_cost, you
> already should be tweaking a lot of stuff yourself anyway.

I think this is a good point.  The people that tend to benefit from the 
lower cost are precisely the people least likely to know to change it.  
It's the "install & go" crowd with smaller databases and only a few 
users/low concurrency that expect it to "just work".  The bigger 
installations are more like to have dedicated DB admins that understand 
tuning.

Wasn't there an idea on the table once to ship with several different 
configuration files with different defaults for small, medium, large, 
etc. installs?  Wouldn't it make sense to ask the user during initdb to 
pick from one of the default config files?  Or even have a few simple 
questions like "How much memory do you expect to be available to 
PostgreSQL?" and "How many concurrent users do you expect to have?".  
It's one thing to know how much memory is in a machine, it quite 
another thing to know how much the user wants dedicated to PostgreSQL.  
A couple of questions like that can go a long way to coming up with 
better ballpark figures.

--
Jeff Hoffmann
jeff@propertykey.com




view thread (5+ messages)  latest in thread

Message-ID: <8dd8c52718f9c9153fe089d64a496150@propertykey.com>
Permalink:  ../8dd8c52718f9c9153fe089d64a496150@propertykey.com/
Also on:    postgresql.org/message-id/8dd8c52718f9c9153fe089d64a496150@propertykey.com

 · 

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: jeff@propertykey.com, greg@turnstep.com
  Subject: Re: Changing the random_page_cost default (was: cpu_tuple_cost)
  In-Reply-To: <8dd8c52718f9c9153fe089d64a496150@propertykey.com>

* 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