From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Volunteer to build a configuration tool
Date: Wed, 20 Jun 2007 01:43:50 -0400
Message-ID: <7621.1182318230@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.4.64.0706200040001.7594@westnet.com>
References: <A3AC4FA47DC0B1458C3E5396E685E63302395E53@SAB-DC1.sab.uiuc.edu>
<1182298719.4482.133.camel@ipso.snappymail.ca>
<Pine.GSO.4.64.0706200040001.7594@westnet.com>
Greg Smith <gsmith@gregsmith.com> writes:
> On Wed, 20 Jun 2007, Mike Benoit wrote:
>> I don't think something like this would be very difficult at all to
>> write
> Here I just smile and say that proves you've never tried to write one :)
I'm with Greg on this. It's not that easy to optimize in a
multi-parameter space even if all conditions are favorable, and they
never are.
I think what would be much more useful in the long run is some
serious study of the parameters themselves. For instance,
random_page_cost is a self-admitted oversimplification of reality.
We know that good settings for it depend critically on how large
your DB is relative to your RAM; which means there are at least two
parameters there, but no one's done any serious thinking about how
to disentangle 'em.
regards, tom lane
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, gsmith@gregsmith.com
Subject: Re: Volunteer to build a configuration tool
In-Reply-To: <7621.1182318230@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