Well, if the solution is a manual workaround that forces a better query plan, this needs to be a part of Postgres itself so it builds better query plans automatically.
The manual workaround is even documented in postgres' wiki <a href="https://wiki.postgresql.org/wiki/Loose_indexscan" rel="nofollow">https://wiki.postgresql.org/wiki/Loose_indexscan
atemerev · · focus · HN ↗
SkiFire13 · · focus · HN ↗