Bruno Wolff III <bruno@wolff.to> writes:
> Bernd Heller <bdheller@users.sourceforge.net> wrote:
>> there is no entry in pg_stats for that column at all!! I can only
>> suspect that this has to do with the column being all null.
> Someone else reported this recently and I think it is going to be fixed.
Yeah, this was griped of a little bit ago, but I felt it was too close
to 8.0 release to risk fooling with for this cycle.
> In the short run you could add an IS NOT NULL clause to your query.
> The optimizer doesn't know that < being TRUE implies IS NOT NULL and
> so the partial index won't be used unless you add that clause explicitly.
Actually, as of 8.0 the optimizer *does* know that. I'm a bit surprised
that it didn't pick the partial index, since even without any analyze
stats, the small physical size of the partial index should have clued it
that there weren't many such tuples. Could we see EXPLAIN output for
both cases (both settings of enable_seqscan)?
regards, tom lane
