From: Richard Broersma Jr <rabroersma@yahoo.com>
To: Arjen van der Meijden <acmmailing@tweakers.net>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Csaba Nagy <nagy@ecircle-ag.com>
Cc: Jim C. Nasby <jim@nasby.net>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Hints proposal
Date: Thu, 12 Oct 2006 14:41:11 -0700 (PDT)
Message-ID: <20061012214111.90031.qmail@web31807.mail.mud.yahoo.com> (raw)
In-Reply-To: <452EAE80.5030501@tweakers.net>
> By the way, wouldn't it be possible if the planner learned from a query
> execution, so it would know if a choice for a specific plan or estimate
> was actually correct or not for future reference? Or is that in the line
> of DB2's complexity and a very hard problem and/or would it add too much
> overhead?
Just thinking out-loud here...
Wow, a learning cost based planner sounds a-lot like problem for control & dynamical systems
theory. As I understand it, much of the advice given for setting PostgreSQL's tune-able
parameters are from "RULES-OF-THUMB." I am sure that effect on server performance from all of the
parameters could be modeled and an adaptive feed-back controller could be designed to tuned these
parameters as demand on the server changes.
Al-thought, I suppose that a controller like this would have limited success since some of the
most affective parameters are non-run-time tune-able.
In regards to query planning, I wonder if there is way to model a controller that could
adjust/alter query plans based on a comparison of expected and actual query execution times.
Regards,
Richard Broersma Jr.
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: rabroersma@yahoo.com, acmmailing@tweakers.net, pgsql@j-davis.com, nagy@ecircle-ag.com, jim@nasby.net
Subject: Re: Hints proposal
In-Reply-To: <20061012214111.90031.qmail@web31807.mail.mud.yahoo.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