Re: Index Scans become Seq Scans after VACUUM ANALYSE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Loftis <mloftis(at)wgops(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE
Date: 2002-04-17 03:58:09
Message-ID: 3212.1019015889@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Loftis <mloftis(at)wgops(dot)com> writes:
> Realistically the system should choos *ANY* index over a sequential
> table scan.

Sorry, I do not accept that. You might as well say that we should
rip out any attempt at cost estimation, and instead put in two or
three lines of brain-dead heuristics. If it were that simple we'd
all be using MySQL ;-)

> Above a fairly low number of records any indexed query
> should be much faster than a seqscan.

Isn't that exactly backwards?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-04-17 04:44:24 Re: Index Scans become Seq Scans after VACUUM ANALYSE
Previous Message Tom Lane 2002-04-17 03:52:53 Re: Index Scans become Seq Scans after VACUUM ANALYSE