4 ms·
Don't forget index statistics, which can turn any query into a full fledged catastrophy if they're not up to date. In my experience it's extremely rare for an
by CaptainZapp 6y ago
Don't forget index statistics, which can turn any query into a full fledged catastrophy if they're not up to date.
In my experience it's extremely rare for an optimizer to go awry on a well maintained database.
And for the rare case where your data - and access patterns are so weird that it does happen you can always employ hints. Which is a bit nasty, granted. But it's not that you would use them excessively on a well designed and maintained database.
It's probably obvious that I very much agree with your take.
- ethbr0 6y agoHints are required in an efficient, general purpose system. Either you can have everything fully-specified at all times (a waste of time an effort, as parent noted), or you can limit general application (no overriding defaults), or you can allow a method for overriding defaults (when necessary). Of those, it seems shortsighted for people to complain about the last, given it's strongly arguably the best of the three options.
- sharadov 6y agoAbsolutely agree.