4 ms·
Shudder. Flashbacks to having to write optimiser hints in Oracle (and the resulting fun times when you'd upgrade the database, something would change, and your
by trollbridge 5mo ago
Shudder. Flashbacks to having to write optimiser hints in Oracle (and the resulting fun times when you'd upgrade the database, something would change, and your hints would make a query slower).
- jeffbee 5mo agoI can't believe we're still doing this. You should be able to dictate the query execution without involving a planner.
- timacles 5mo agoI really don’t think you’re considering all the edge cases in such a scenario. Most devs have problems writing decent queries (in some situations), now you want to introduce writing the query execution plan into the mix ?
- akoboldfrying 5mo agoNo one is taking away the existing automatic planning that works well 95% of the time. You're welcome to continue using that. The worst thing that could possibly happen is that you give it bad advice leading to slow queries, and then the obvious first step to fixing that is to drop the manual advice and see whether the automatic planner handles it better. It baffles me that PostgreSQL, which is so deeply customisable in almost every other way, resisted this form of customisability for so long. This is great news.
- winrid 5mo agoAs opposed to not upgrading and the planner picking a plan at 3am that is slower?
- deleted 5mo ago[deleted]