| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(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:09:16 |
| Message-ID: | 16144.959965756@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Peterson | 2000-06-02 19:36:17 | Sample Program 2 - libpq |
| Previous Message | Bruce Momjian | 2000-06-02 17:00:32 | Re: query optimiser changes 6.5->7.0 |