Postgres 19 query hints signal a maturing planner relationship
The Postgres 19 query hints post is getting warm reception from practitioners who have spent years fighting the query planner with hacks like enable_seqscan = off and OFFSET 0 subquery tricks. The new pg_plan_advice extension offers a readable, composable syntax for giving the planner explicit guidance without those workarounds. The thread includes people sharing specific production cases where planner hints would have saved real debugging time.
This is a niche but meaningful shift. Postgres has historically been resistant to hints, arguing that improving the planner is better than letting users override it. Adding hints is an acknowledgment that the planner can't always win, and that giving experienced users a clean override mechanism is better than the current state of creative hacks.
The design getting praised specifically is the syntax, which is readable and composable in a way that Oracle-style hints are not. That matters for code review and long-term maintainability.
So what?
If you're running complex queries in Postgres at scale, query hints in Postgres 19 could replace a class of performance workarounds that are currently brittle and hard to document. Worth testing on your slowest queries before it ships. For infrastructure-focused founders, this is a signal that Postgres is taking production performance concerns more seriously than its historical stance suggested.