Re: Index Scans become Seq Scans after VACUUM ANALYSE
Peter Eisentraut <peter_e@gmx.net>
From: Peter Eisentraut <peter_e@gmx.net>
To: mlw <markw@mohawksoft.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Lockhart <thomas@fourpalms.org>, Lincoln Yeoh <lyeoh@pop.jaring.my>, Bruce Momjian <pgman@candle.pha.pa.us>, Louis-David Mitterrand <vindex@apartia.org>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2002-04-17T18:32:19Z
Lists: pgsql-hackers
mlw writes: > Adding huristics, such as weighting for index scans, is not making the planner > stupider. It is making it smarter and more flexable. If life was as simple as index or no index then this might make some sense. But in general the planner has a whole bunch of choices of join plans, sorts, scans, and the cost of an individual index scan is hidden down somewhere in the leaf nodes, so you can't simply say that plans of type X should be preferred when the cost estimates are close. -- Peter Eisentraut peter_e@gmx.net