On 11/17/13 9:18 PM, Tom Lane wrote:
> Marko Tiikkaja <marko@joh.to> writes:
>> Any suggestions for a workaround? When reading this index as a part of
>> a bigger query the horrible estimate ensures that nobody's having fun.
>
> Why is the estimate so bad? I suppose the answer is that those two
> columns are very strongly correlated. Maybe you could refactor your
> data representation to avoid that?
I'll look into that, thanks.
> The long-term answer as far as Postgres is concerned is to learn about
> cross-column correlations, but that's not happening in the near future.
I'm completely clueless about how the planner works, but wouldn't it be
easier to have some kind of separate stats for the conditions in partial
indexes? It seems better in all cases than trying infer the stats from
cross-column correlations, even if we had that.
Regards,
Marko Tiikkaja
