Although, I suspect the (dropped index + enable_seqscan) causes this, is the cost shown in explain output some kind of default max or something like that for such abnormal cases?
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.
