Some versions of these RDBMS perform poorly with history queries, particularly
when the optimizer changes join order or uses block nested loop joins. Ideally,
testing across all RDBMS versions to identify when the optimizer fails and
adjusting queries or using optimizer switches would be preferable, but this
level of effort is not justified at the moment.
Optimizer is disabled via config:
`/etc/icingaweb2/modules/icingadb/config.ini`:
```
[icingadb]
...
disable_optimizer_for_history_queries=1
```
