From: Craig A. James <cjames@modgraph-usa.com>
To: pgsql-performance@postgresql.org
Subject: Re: Hints proposal
Date: Sun, 15 Oct 2006 17:25:31 -0700
Message-ID: <4532D17B.20106@modgraph-usa.com> (raw)
In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4209CBF@MAIL.corp.lumeta.com>
References: <78ED28FACE63744386D68D8A9D1CF5D4209CBF@MAIL.corp.lumeta.com>
So let's cut to the bone: If someone thinks a proposal is a bad idea, and they're volunteering their time on an open-source project, why would they implement the proposal?
In all the heat and smoke, I believe there are two basic conclusions we all agree on.
1. Optimizer:
a) A perfect optimizer would be a wonderful thing
b) Optimization is a hard problem
c) Any problem that can be solve by improving the optimizer *should*
be solved by improving the optimizer.
2. Hints
a) On a aesthetic/theoretical level, hints suck. They're ugly and rude
b) On a practical level, introducing hints will cause short- and long-term problems
c) Hints would help DBAs solve urgent problems for which there is no other solution
The disagreements revolve around the degree to which 1 conflicts with 2.
1. Developers feel very strongly about 2(a) and 2(b).
2. DBAs "in the trenches" feel very strongly about 2(c).
So my question is: Is there any argument that can be made to persuade those of you who are volunteering your time on the optimizer to even consider a HINTS proposal? Has all this discussion changed your perspective on 2(c), and why it really matters to some of us? Are we just wasting our time, or is this a fruitful discussion?
Thanks,
Craig
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: cjames@modgraph-usa.com
Subject: Re: Hints proposal
In-Reply-To: <4532D17B.20106@modgraph-usa.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