PostgreSQL BRIN Indexes: When & How to Use Block Range Indexes

PostgreSQL BRIN Indexes: When & How to Use Block Range Indexes You have a 500-million-row events table. The B-tree index on created_at consumes 12 GB. Every insert must update that 12 GB index. Backups include 12 GB of index data. The buffer cache is full of index pages. And all you ever do is range queries: "give me events from last week." There's a better way. A BRIN index on the same column would be roughly 100 KB -- not 12 GB -- and for your query pattern, it works just as well. How BRIN