Simple Postgres Query Optimization: Avoid the Sequential Scan | Dark Hacker News