Horton

Re: query optimiser changes 6.5->7.0

Bruce Momjian <pgman@candle.pha.pa.us>

View thread View on postgr.es
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.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:00:32Z
Lists: pgsql-general 
> 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?  Seems people have been asking for fine-tuned optimizer control.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026