> ... Wouldn't the most efficient plan be to scan the index regardless
> of crm_id because the only columns needed are in the index?
No. People coming from other databases often have the misconception
that queries can be answered by looking only at an index. That is never
true in Postgres because row validity info is only stored in the table;
so we must always visit the table entry to make sure the row is still
valid/visible for the current query.
Accordingly, columns added to the index that aren't constrained by the
WHERE clause are not very useful ...
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Gary Doades||Date: 2004-04-28 06:35:41|
|Subject: Re: planner/optimizer question |
|Previous:||From: Christopher Kings-Lynne||Date: 2004-04-28 01:30:44|
|Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the|