Its also worth reading the original post by Robert Haas (the author of pg_plan_advice) on motivation/design: <a href="https://rhaas.blogspot.com/2026/03/pgplanadvice-plan-stability-and-user.html" rel="nofollow">https://rhaas.blogspot.com/2026/03/pgplanadvice-plan-stabili...</a><p>Also, I'll add my perspective: I think "EXPLAIN (PLAN_ADVICE)" is a key piece to making this a plan stability feature, not (just) a hinting feature. The extensibility/framework pg_plan_advice adds is a foundation, that over time will over time address the age-old "Postgres doesn't have hints" problem, even if the initial release doesn't check all the boxes yet, e.g. no way to use advice for adjusting row/join estimates.<p>To give an example on extensibility: Some people that I've spoken to are asking "but why is it not a comment-style hint". There are reasons why Postgres didn't go that way for this release (comment parsing in core is non-existent today, and comments don't work correctly e.g. for functions), but its easy to write an extension that sets up an advisor hook to parse comments: <a href="https://github.com/pganalyze/pg_advice_comment" rel="nofollow">https://github.com/pganalyze/pg_advice_comment</a>