update_database_disk_utilization fails with GIN indexes
Bug #1007333 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Stuart Bishop | ||
Bug Description
pgstattuple does not support GIN indexes so the query to collect disk statistics fails. We need to exclude GIN indexes when collecting disk utilization information until this is supported.
Related branches
lp:~stub/launchpad/pending-db-changes
- Stuart Bishop (community): Approve (db)
- Diff: 0 lines
- Launchpad code reviewers: Pending requested
-
Diff: 1281 lines (+989/-8) (has conflicts)16 files modifieddatabase/schema/patch-2209-21-4.sql (+111/-0)
lib/lp/app/browser/tales.py (+14/-5)
lib/lp/app/templates/banner-macros.pt (+50/-0)
lib/lp/archivepublisher/debian_installer.py (+27/-0)
lib/lp/archivepublisher/tests/test_debian_installer.py (+150/-0)
lib/lp/archivepublisher/tests/test_dist_upgrader.py (+89/-0)
lib/lp/bugs/browser/bugtarget.py (+8/-0)
lib/lp/bugs/browser/tests/test_bugtarget_filebug.py (+93/-0)
lib/lp/bugs/javascript/filebug.js (+78/-0)
lib/lp/bugs/javascript/tests/test_filebug.html (+106/-0)
lib/lp/bugs/javascript/tests/test_filebug.js (+116/-0)
lib/lp/code/model/tests/test_branch.py (+35/-0)
lib/lp/code/model/tests/test_branchlookup.py (+6/-0)
lib/lp/code/model/tests/test_branchvisibility.py (+9/-0)
lib/lp/soyuz/tests/test_distroseriesqueue_debian_installer.py (+77/-0)
lib/lp/testing/factory.py (+20/-3)
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| assignee: | nobody → Stuart Bishop (stub) |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #1 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in db-stable r11640 <http://