Re: Index Scans become Seq Scans after VACUUM ANALYSE
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lincoln Yeoh <lyeoh@pop.jaring.my>
Cc: mlw <markw@mohawksoft.com>, Bruce Momjian <pgman@candle.pha.pa.us>, Andrew Sullivan <andrew@libertyrms.info>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2002-04-20T04:16:15Z
Lists: pgsql-hackers
Lincoln Yeoh <lyeoh@pop.jaring.my> writes: > ...By the way, are updates treated the same as selects by the optimizer? Yeah. The writes must occur in any case, so I see no reason why the optimizer should worry about them. All it needs to consider are the cycles used by the various alternatives for fetching the data. So the problem is isomorphic to a SELECT. This assumption is really wired quite fundamentally into the optimizer, but I'm not sure if it's made clear anywhere in the documentation. Can anyone suggest the right place to describe it? regards, tom lane