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 #10066] Missing indexes for icinga_endpoints* and icinga_zones* tables in DB IDO schema #3361
Comments
Updated by tgelf on 2015-09-01 14:11:02 +00:00 Same goes for icinga_zones and icinga_zonestatus |
Updated by mfriedrich on 2015-09-01 14:21:04 +00:00
|
Updated by mfriedrich on 2015-09-04 09:21:54 +00:00
|
Updated by mfriedrich on 2016-01-23 11:47:39 +00:00
|
Updated by mfriedrich on 2016-06-22 10:16:22 +00:00
|
Updated by mfriedrich on 2016-06-22 10:49:36 +00:00
MySQLicinga_endpoints{,tatus}
icinga_zones{,tatus}
The first entry would use the index, but it seems that MySQL assumes a full table join and doesn't use the index here. Same goes for the endpoint tables. PostgreSQL
--
|
Updated by mfriedrich on 2016-06-22 10:57:17 +00:00
Applied in changeset 7f56a04. |
Updated by mfriedrich on 2016-11-11 08:46:51 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10066
Created by tgelf on 2015-09-01 12:33:42 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-06-22 10:57:17 +00:00)
Target Version: 2.5.0
Last Update: 2016-11-11 08:46:51 +00:00 (in Redmine)
It's a new feature and rarely used, still tables should get meaningful indexes.
Changesets
2016-06-22 10:56:24 +00:00 by mfriedrich 7f56a04
Relations:
The text was updated successfully, but these errors were encountered: