You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created by mfriedrich on 2016-07-06 09:56:10 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-07-06 10:20:04 +00:00)
Target Version: 2.5.0
Last Update: 2016-07-06 10:20:04 +00:00 (in Redmine)
Icinga Version: 2.4.10
Backport?: Not yet backported
Include in Changelog: 1
CREATE INDEX idx_statehistory_cleanup on icinga_statehistory(instance_id, state_time);
The mysql query optimiser will decide upon the given comparison (state_time > $datetime) whether an index or a full table scan is required. Currently the DELETE operations from inside the IDO feature depends on a proper index.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12107
Created by mfriedrich on 2016-07-06 09:56:10 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-07-06 10:20:04 +00:00)
Target Version: 2.5.0
Last Update: 2016-07-06 10:20:04 +00:00 (in Redmine)
The mysql query optimiser will decide upon the given comparison (state_time > $datetime) whether an index or a full table scan is required. Currently the DELETE operations from inside the IDO feature depends on a proper index.
http://stackoverflow.com/questions/18297509/mysql-index-on-timestamp-column-not-used-for-large-date-ranges
Changesets
2016-07-06 10:17:41 +00:00 by mfriedrich a0a5989
The text was updated successfully, but these errors were encountered: