Re: generalizing the planner knobs - Mailing list pgsql-hackers

From Pollard, Mike
Subject Re: generalizing the planner knobs
Date
Msg-id 6418CC03D0FB1943A464E1FEFB3ED46B01B220F2@im01.cincom.com
Whole thread Raw
In response to generalizing the planner knobs  (Neil Conway <neilc@samurai.com>)
Responses Re: generalizing the planner knobs  (Gregory Maxwell <gmaxwell@gmail.com>)
Re: generalizing the planner knobs  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Greg Stark <gsstark@mit.edu> writes:
> On the other hand the type I would prefer to see are hints that feed
directly
> into filling in information the planner lacks. This only requires that
the
> user understand his own data and still lets the planner pick the best
plan
> based on the provided information.

Optimizer hints were added because some databases just don't have a very
smart optimizer.  But you are much better served tracking down cases in
which the optimizer makes a bad choice, and teaching the optimizer how
to make a better one.  That way, all users get the benefit of the fix.
Remember, the purpose of SQL is to isolate the end user from having to
care about how the data is retrieved; that is the RDBMS' problem.  (the
other thing forgotten was that it was supposed to be a natural language.
NVL.  Bah.)

Mike Pollard
SUPRA Server SQL Engineering and Support
Cincom Systems, Inc.




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [COMMITTERS] pgsql: Add comments about why errno is set to zero.
Next
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Add comments about why errno is set to zero.