"Nick Fankhauser" <nickf@ontko.com> writes:
> [see subject]
Nope, they ain't. I agree they should be.
> Can someone tell me how the cost is estimated for retrieving a column based
> on a function that is indexed?
It falls back to a default selectivity estimate, which is something
like 1% or 0.5% (depending on which version you are running).
> Also, even with 2168 rows to gather, my experience based on cases where
> several thousand rows really are returned indicates that the index would
> still be a good choice. Is there a way to make the planner favor index scans
> a bit more? (Other than the drastic set enable_seqscan to off.)
I'd suggest reducing random_page_cost; we've seen a number of anecdotal
reports that the default of 4.0 is too high, though nothing systematic
enough to refute the experiments I did to get that number awhile back.
(IMHO anyway. Others may differ.)
regards, tom lane
