ByteBrief
We're a portrait publication through and through. Turn your phone back and your briefing picks up right where you left it.
(We tried widescreen once. It wasn't us.)

PostgreSQL's EXPLAIN ANALYZE separates Planning Time from Execution Time, and misreading the split leads to wasted optimization. On a 500-partition table, planning took 62.9 ms versus 7.2 ms execution, with the planner reading 20,063 blocks versus 932 for execution. Indexes worsen planning problems; work_mem and storage layout fix execution ones.
Tap to vote and see what everyone thinks.
Summary by ByteBrief