From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Martijn van Oosterhout <kleptog(at)cupid(dot)suninternet(dot)com>, Alfred Perlstein <bright(at)wintelcom(dot)net>, Wim Ceulemans <wim(dot)ceulemans(at)nice(dot)be>, Joseph Shraibman <jks(at)selectacast(dot)net>, Simon Hardingham <simon(at)netxtra(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: query optimiser changes 6.5->7.0 |
Date: | 2000-06-02 17:00:32 |
Message-ID: | 200006021700.NAA26291@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-02 17:09:16 | Re: query optimiser changes 6.5->7.0 |
Previous Message | The Hermit Hacker | 2000-06-02 16:49:19 | PostgreSQL v7.0.1 Released |