HN Reader

I’m still waiting for the future where planner is a plugin for db.

Seems this is a (small) step in that direction

I've used Pg since 2005. In 2025 my team finally had to resort to pg_hint_plan, which I had thankfully already allow-listed. It was a lifesaver when the planner just wouldn't use the optimal index.

(Seen at least two occasions where MySQL needed hints, and once where it needed odd bool and date comparisons.)

Looking forward to dropping the hint as soon as a new, major Pg version no longer needs it.

Thanks for posting! There is a hand-edited transcript here as well, for those who prefer text: https://pganalyze.com/blog/5mins-postgres-19-better-planner-...

And, its noted in the video/transcript, but for clarity: This is talking about new extensibility in Postgres 19 that makes it easier to do Postgres planner hints / plan management extensions.

The patch that was committed is part of a larger proposal (pg_plan_advice) which, if it ends up being committed, would add a version of planner hints to Postgres itself (in contrib). It remains to be seen where that goes for Postgres 19.

- any chance of vector support beyond pg-vector?