New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #10070] IDO: there is no usable object index on icinga_{scheduleddowntime,comments} #3365
Comments
Updated by mfriedrich on 2015-09-01 14:21:15 +00:00
|
Updated by mfriedrich on 2015-09-04 09:21:58 +00:00
|
Updated by mfriedrich on 2016-01-23 11:47:41 +00:00
|
Updated by tobiasvdk on 2016-06-20 13:54:56 +00:00
|
Updated by mfriedrich on 2016-06-20 14:11:18 +00:00
|
Updated by mfriedrich on 2016-06-20 14:19:23 +00:00
|
Updated by mfriedrich on 2016-06-20 14:20:14 +00:00
|
Updated by mfriedrich on 2016-06-20 14:30:04 +00:00
Applied in changeset a86e381. |
Updated by mfriedrich on 2016-11-11 08:46:54 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10070
Created by tgelf on 2015-09-01 12:44:40 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-06-20 14:30:04 +00:00)
Target Version: 2.5.0
Last Update: 2016-11-11 08:46:54 +00:00 (in Redmine)
This makes queries joining downtime information to objects unnecessarily expensive.
Changesets
2016-06-20 14:23:57 +00:00 by mfriedrich a86e381
2016-06-20 15:15:09 +00:00 by mfriedrich f10289a
Relations:
The text was updated successfully, but these errors were encountered: