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?
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.
regards, tom lane