pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas F.O'Connell <tfo@sitening.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tambet Matiisen <t.matiisen@aprote.ee>
Cc: pgsql-performance@postgresql.org
Subject: Re: What about utility to calculate planner cost constants?
Date: Mon, 21 Mar 2005 12:18:17 -0600
Message-ID: <11322edfb476c82809712b9796f78a5f@sitening.com> (raw)
In-Reply-To: <200503210951.06044.josh@agliodbs.com>
References: <A66A11DBF5525341AEF6B8DE39CDE77008805C@black.aprote.com>
	<200503210951.06044.josh@agliodbs.com>

If by not practical you mean, "no one has implemented a multivariable 
testing approach," I'll agree with you. But multivariable testing is 
definitely a valid statistical approach to solving just such problems.

-tfo

--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005

On Mar 21, 2005, at 11:51 AM, Josh Berkus wrote:

> That's not really practical.   There are currently 5 major query tuning
> parameters, not counting the memory adjustments which really can't be 
> left
> out.  You can't realistically test all combinations of 6 variables.




view thread (21+ messages)  latest in thread

Message-ID: <11322edfb476c82809712b9796f78a5f@sitening.com>
Permalink:  ../11322edfb476c82809712b9796f78a5f@sitening.com/
Also on:    postgresql.org/message-id/11322edfb476c82809712b9796f78a5f@sitening.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: tfo@sitening.com, josh@agliodbs.com, t.matiisen@aprote.ee
  Subject: Re: What about utility to calculate planner cost constants?
  In-Reply-To: <11322edfb476c82809712b9796f78a5f@sitening.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