News for hackers. Stuff that matters.

A comment on What's new in the Postgres 16 query planner (a.k.a. optimizer). Parent comment

Re:What's new in the Postgres 16 query planner (a.k.a. optim... by somat on Friday February 09, 2024 @02:45AM (#39312472)
I suspect the ideological problem with hints is that if the planner is producing a poor query, then the correct place to fix that is in the planner.

While I agree with this viewpoint, The problem is that most people don't want to be a Postgress dev, To actually enable people to fix the planner it would have to be exposed as a runtime service. And unless there was a lot of diligence the planner script would quickly degrade into an unmaintainable mess(low blow: just like most schemas.)

[ Parent | on HN ]
Re:What's new in the Postgres 16 query planner (a.k.a. optim... by williamdclt on Friday February 09, 2024 @05:05AM (#39313305)
I don't think anybody disagrees that the correct place to fix that is the planner, people just want an escape hatch so that when poor queries happen they can do _something_ instead of waiting for a fix to be written, a release to include it, and upgrading their database. It's a pretty reasonable ask, I think!
[ Parent | on HN ]