Re: query optimiser changes 6.5->7.0

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Martijn van Oosterhout <kleptog@cupid.suninternet.com>, Alfred Perlstein <bright@wintelcom.net>, Wim Ceulemans <wim.ceulemans@nice.be>, Joseph Shraibman <jks@selectacast.net>, Simon Hardingham <simon@netxtra.net>, pgsql-general@postgresql.org
Date: 2000-06-02T17:09:16Z
Lists: pgsql-general
Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> So, while I have been known to suggest "set enable_seqscan=off" and
>> friends when there seemed no other short-term answer, I don't want to
>> enshrine it as a standard recommendation.  It's just a way of plugging
>> holes in the dike until more planner work gets done.

> They can certainly turn of off before a query and on after the query,
> right?

Sure, that's how I'd suggest using it at the moment.

> Seems people have been asking for fine-tuned optimizer control.

I know, but I think that's the wrong direction to go in, for the reasons
I tried to explain.  The more specific the command you give to force
a particular query plan, the more likely that command is to go wrong
as the situation changes.

			regards, tom lane