Jira (PDB-3220) resource_events_resource_type_idx should be removed because it's unused and duplicates resource_events_resource_timestamp

[Nick Walker (JIRA)]

Title: Message Title

Nick Walker created an issue   PuppetDB / PDB-3220 resource_events_resource_type_idx should be removed because it's unused and duplicates resource_events_resource_timestamp Issue Type: Improvement Assignee: Unassigned Created: 2016/12/08 11:49 AM Labels: tcse Priority: Normal Reporter: Nick Walker The Problem \d+ resource_events ... Indexes: ... "resource_events_resource_timestamp" btree (resource_type, resource_title, "timestamp") ... "resource_events_resource_type_idx" btree (resource_type) The database can execute the same searches on the timestamp index because they both have the same primary column. An argument for keeping the resource_type index would be if the timestamp index were significantly larger and wasn't as fast to search since it has the each column data in it. However, based on some pdb-summary-stats data I have it appears the resource_type_idx is never used because the optimizer must prefer the timestamp index for some reason. We could confirm with more summary stats data but if the usage of the resource_types index is low then having queries use the timestamp index should be of marginal difference. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.