Re: Overriding the optimizer - Mailing list pgsql-performance

From Kevin Brown
Subject Re: Overriding the optimizer
Date
Msg-id 20051216052025.GB691@filer
Whole thread Raw
In response to Re: Overriding the optimizer  ("Craig A. James" <cjames@modgraph-usa.com>)
Responses Re: Overriding the optimizer  ("Craig A. James" <cjames@modgraph-usa.com>)
Re: Overriding the optimizer  (Kyle Cordes <kyle@kylecordes.com>)
List pgsql-performance
Craig A. James wrote:
> Hints are dangerous, and I consider them a last resort.

If you consider them a last resort, then why do you consider them to
be a better alternative than a workaround such as turning off
enable_seqscan, when all the other tradeoffs are considered?

If your argument is that planner hints would give you finer grained
control, then the question is whether you'd rather the developers
spend their time implementing planner hints or improving the planner.
I'd rather they did the latter, as long as workarounds are available
when needed.  A workaround will probably give the user greater
incentive to report the problem than use of planner hints.


--
Kevin Brown                          kevin@sysexperts.com

pgsql-performance by date:

Previous
From: Kevin Brown
Date:
Subject: Re: Overriding the optimizer
Next
From: "Craig A. James"
Date:
Subject: Re: Overriding the optimizer