| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Thomas Lockhart" <thomas(at)fourpalms(dot)org>, "mlw" <markw(at)mohawksoft(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Louis-David Mitterrand" <vindex(at)apartia(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index Scans become Seq Scans after VACUUM ANALYSE |
| Date: | 2002-04-17 14:56:20 |
| Message-ID: | 00a101c1e620$09a450b0$0200a8c0@SOL |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Systems which have optimizing planners can *never* be guaranteed to
> generate the actual lowest-cost query plan. Any impression that Oracle,
> for example, actually does do that may come from a lack of visibility
> into the process, and a lack of forum for discussing these edge cases.
Hmmm...with PREPARE and EXECUTE, would it be possible to somehow get the
planner to actually run a few different selects and then actually store the
actual fastest plan? I'm being very fanciful here, of course...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mlw | 2002-04-17 14:57:17 | Re: Index Scans become Seq Scans after VACUUM ANALYSE |
| Previous Message | Thomas Lockhart | 2002-04-17 14:55:36 | Re: Index Scans become Seq Scans after VACUUM ANALYSE |