From: | mlw <markw(at)mohawksoft(dot)com> |
---|---|
To: | Thomas Lockhart <thomas(at)fourpalms(dot)org> |
Cc: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>, 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 15:22:37 |
Message-ID: | 3CBD933D.BF873518@mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From:
mlw <markw(at)mohawksoft(dot)com>
11:05
Subject:
Re: Index Scans become Seq Scans after VACUUM ANALYSE
To:
Thomas Lockhart <thomas(at)fourpalms(dot)org>
Thomas Lockhart wrote:
>
> ...
> > Weighing these factors, perhaps once we get one or two complaining about
> > postgresql using an index vs 20 complaining about not using an index, then
> > the optimizer values have reached a good compromise :). But maybe the ratio
> > should be 1 vs 100?
>
> :)
>
> So we should work on collecting those statistics, rather than statistics
> on data. What do you think Tom; should we work on a "mailing list based
> planner" which adjusts numbers from, say, a web site? That is just too
> funny :)))
No, you miss the point!
On borderline conditions, wrongly using an index does not result in as bad
performance as wrongly not using an index, thus usage of an index should be
weighted higher because the risk of not using the index out weighs the risk of
using it.
From | Date | Subject | |
---|---|---|---|
Next Message | Louis-David Mitterrand | 2002-04-17 15:26:33 | Re: huge runtime difference between 2 almost identical queries (was: Re: Index Scans become Seq Scans after VACUUM ANALYSE) |
Previous Message | Tom Lane | 2002-04-17 15:19:12 | Re: date_in function |