Re: Super Optimizing Postgres

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Clift <justin(at)postgresql(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, mlw <markw(at)mohawksoft(dot)com>, matthew(at)zeut(dot)net, Alex Pilosov <alex(at)pilosoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Super Optimizing Postgres
Date: 2001-11-17 05:14:34
Message-ID: 20174.1005974074@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Justin Clift <justin(at)postgresql(dot)org> writes:
> I think it's an interesting thought of having a program which will test
> a system and work out the Accurate and Correct values for this.

I think if you start out with the notion that there is an Accurate
and Correct value for these parameters, you've already lost the game.
They're inherently fuzzy numbers because they are parameters of an
(over?) simplified model of reality.

It would be interesting to try to fit the model to reality on a wide
variety of queries, machines & operating environments, and see what
numbers we come up with. But there's always going to be a huge fuzz
factor involved. Because of that, I'd be *real* wary of any automated
tuning procedure. Without a good dollop of human judgement in the loop,
an automated parameter-setter will likely go off into never-never land
:-(

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masaru Sugawara 2001-11-17 06:31:32 Re: regress test db
Previous Message Bruce Momjian 2001-11-17 05:09:58 Re: TOAST performance (was Re: [GENERAL] Delete Performance)