certain table columns are not indexed that should be
Bug #845847 reported by
Chris Behrens
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
'uuid' in instances table should be indexed, for one... as well as 'reservation_id'.
Other columns in the instances table that people might commonly filter on probably should be as well. display_name and power_state are in the API spec.
I haven't checked other tables.
| Changed in nova: | |
| assignee: | nobody → Josh Kearney (jk0) |
| status: | New → In Progress |
| Changed in nova: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Josh Kearney (jk0) wrote | #1 |
| Changed in nova: | |
| status: | In Progress → Won't Fix |
| assignee: | Josh Kearney (jk0) → nobody |
To post a comment you must log in.
Per Jay Pipes:
Patch Set 2: I would prefer that you didn't submit this
I don't think we should be adding migration files for database optimization... what works for some doesn't work for other installations with different data querying patterns. This is more DBA work.
Now, adding unique indexes that enforce *constraints* on data is another thing entirely, but I don't agree we should be doing a DBA's work in trying to prematurely predict which columns need indexes for performance reasons...