pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marinos J. Yannikos <mjy@geizhals.at>
Cc: pgsql-performance@postgresql.org
Subject: Re: why do optimizer parameters have to be set manually?
Date: Thu, 18 Dec 2003 14:56:20 -0500
Message-ID: <22686.1071777380@sss.pgh.pa.us> (raw)
In-Reply-To: <3FE1F5A1.6080908@geizhals.at>
References: <3FE1F5A1.6080908@geizhals.at>

"Marinos J. Yannikos" <mjy@geizhals.at> writes:
> it seems to me that the optimizer parameters (like random_page_cost 
> etc.) could easily be calculated and adjusted dynamically be the DB 
> backend based on the planner's cost estimates and actual run times for 
> different queries. Perhaps the developers could comment on that?

No, they are not that easy to determine.  In particular I think the idea
of automatically feeding back error measurements is hopeless, because
you cannot tell which parameters are wrong.

> I'm not sure how the parameters are used internally (apart from whatever 
> "EXPLAIN" shows), but if cpu_operator_cost is the same for all 
> operators, this should probably also be adjusted for individual 
> operators (I suppose that ">" is not as costly as "~*").

In theory perhaps, but in practice this is far down in the noise in most
situations.

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <22686.1071777380@sss.pgh.pa.us>
Permalink:  ../22686.1071777380@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22686.1071777380@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, mjy@geizhals.at
  Subject: Re: why do optimizer parameters have to be set manually?
  In-Reply-To: <22686.1071777380@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