Replication lag checks do not understand PG 9.1 streaming replication

Bug #1014661 reported by Stuart Bishop
6
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

Stuart Bishop (stub)
Changed in launchpad:
importance: Undecided → High
assignee: nobody → Stuart Bishop (stub)
status: New → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Revision history for this message
Stuart Bishop (stub) wrote :

qastaging continues to run with this update, so qa-ok. Once this is on staging too, we can update the staging dbs and confirm the load balancing works as desired.

tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Stuart Bishop (stub) wrote :

Discovered a database started in recovery mode, such as after a hard shutdown, was detected as a lagged replica causing tests to fail. Need to update the check to only report xlog replay time as lag when the database is actually a hot standby.

Stuart Bishop (stub)
tags: added: qa-bad
removed: qa-ok
William Grant (wgrant)
tags: added: bad-commit-15448
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-bad
Changed in launchpad:
status: In Progress → Fix Committed
William Grant (wgrant)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
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.