Seems like it might have more legs than the usual "postgres should get query hints" requests that the PG team generally don't entertain.
> "I think we've become so negative about hints that we rarely have a rational discussion about them... I also don't enjoy telling a customer 'hey, I know this query started misbehaving in the middle of the night on Christmas, but hints are bad... you can just have your web site be down for the next 20 years while we try to improve the optimizer.'"
Above quote is from the author of pg_plan_advice itself, from a few years ago.
So given his proposal isn't just band-aiding query hints into PG, is from a committer instead of being a drive-by patch, and might be even more generally useful/applicable than "add query hints" - maybe we could see some movement here.
> "I think we've become so negative about hints that we rarely have a rational discussion about them... I also don't enjoy telling a customer 'hey, I know this query started misbehaving in the middle of the night on Christmas, but hints are bad... you can just have your web site be down for the next 20 years while we try to improve the optimizer.'"
https://www.mail-archive.com/[email protected]....
Above quote is from the author of pg_plan_advice itself, from a few years ago.
So given his proposal isn't just band-aiding query hints into PG, is from a committer instead of being a drive-by patch, and might be even more generally useful/applicable than "add query hints" - maybe we could see some movement here.