> When one uses “enable_” settings to adjust planner behavior, PostgreSQL
> just sets really high costs for the operations affected (like the one you
> see).
>
> As SeqScan is the only possible way to execute your query, it is still
> choosen.
>
I get it. Thanks!
--
Amit Langote