database not always correctly republished by hot standbys
Bug #1278731 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| postgresql (Juju Charms Collection) |
Fix Released
|
High
|
Stuart Bishop | ||
Bug Description
Hot standby units publish database connection details, but are not notified when a client has changed its database name and thus fail to republish connection details with the correct database name. Clients are supposed to check for a matching database name, and may never see the correct one set.
Related branches
lp:~stub/charms/precise/postgresql/bug-1278731-hot-standby-allowed-units
- Marco Ceppi (community): Approve
-
Diff: 80 lines (+30/-8)2 files modifiedhooks/hooks.py (+13/-4)
test.py (+17/-4)
| summary: |
- allowed-units not published by hot standbys + database not always correctly republished by hot standbys |
| description: | updated |
| Changed in postgresql (Juju Charms Collection): | |
| status: | New → Invalid |
| status: | Invalid → New |
| Changed in postgresql (Juju Charms Collection): | |
| status: | New → In Progress |
| assignee: | nobody → Stuart Bishop (stub) |
| importance: | Undecided → High |
| Changed in postgresql (Juju Charms Collection): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
