database bloat report ordering needs tuning

Bug #757298 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Stuart Bishop

Bug Description

Per https://devpad.canonical.com/~lpqateam/dbr/daily/db-report-%5C2011-%5C04-%5C10.txt , the ordering is broken. High bloat, high wasted space indexes are way down the list.

Related branches

Revision history for this message
Stuart Bishop (stub) wrote :

(remove that example report when closing this bug)

Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Stuart Bishop (stub)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.05
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
Stuart Bishop (stub)
tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui)
Changed in launchpad:
status: Fix Committed → Fix Released
Revision history for this message
Francis J. Lacoste (flacoste) wrote :

This should have been a High bug.

tags: added: critical-analysis
Changed in launchpad:
importance: Critical → High
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 757298] Re: database bloat report ordering needs tuning

It was critical by inheritance: we had performance timeouts due to index bloat.

Changed in launchpad:
importance: High → Medium
importance: Medium → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.