Replication lag checks do not understand PG 9.1 streaming replication
Bug #1014661 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Stuart Bishop |
Bug Description
The replication lag checks only support Slony-I replication. They need to support both Slony-I and PostgreSQL 9.1 streaming replication so we can migrate.
Related branches
lp://staging/~stub/launchpad/replication
- Abel Deuring (community): Approve (code)
- Aaron Bentley (community): Approve
-
Diff: 196 lines (+106/-19)7 files modifieddaemons/cache-database-replication-lag.py (+53/-0)
database/replication/helpers.py (+1/-0)
database/schema/comments.sql (+4/-0)
database/schema/patch-2207-28-1.sql (+9/-0)
database/schema/security.cfg (+6/-0)
database/schema/trusted.sql (+22/-0)
lib/canonical/launchpad/webapp/dbpolicy.py (+11/-19)
Changed in launchpad: | |
importance: | Undecided → High |
assignee: | nobody → Stuart Bishop (stub) |
status: | New → In Progress |
tags: |
added: qa-bad removed: qa-ok |
tags: | added: bad-commit-15448 |
Changed in launchpad: | |
status: | Fix Committed → In Progress |
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 stable r15444 <http:// bazaar. launchpad. net/~launchpad- pqm/launchpad/ stable/ revision/ 15444>.