When our 2TB time-series table’s B-tree index hit 18GB, query latency spiked to 2.1s and vacuum operations took 14 hours. Switching to PostgreSQL 17’s BRIN indexes cut index size to 180MB—100x smaller—slashed p99 latency to 89ms, and reduced vacuum time to 47 minutes. Here’s exactly how we did it, with benchmark-backed code and real-world tradeoffs. 📡 Hacker News Top Stories Right Now Why does it take so long to release black fan versions? (256 points) How fast is a macOS VM, and how small could it be? (11 points) Why are there both TMP and TEMP environment variables? (2015) (21 points) Show HN: Mljar Studio – local AI data analyst that saves analysis as notebooks (3 points) Show HN: DAC – open-source dashboard as code tool for agents and humans (11 points) Key Insights PostgreSQL 17 BRIN indexes for time-series tables with sequential, monotonically increasing timestamps deliver 100x size reduction over equivalent B-tree indexes at 2TB scale.…