Report question

Question: PostgreSQL query planner choosing sequential scan despite btree index on large table