Merge lp://staging/~stub/charms/precise/postgresql/old-replication into lp://staging/charms/postgresql
Proposed by
Stuart Bishop
| Status: | Merged | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Approved by: | Mark Mims | ||||||||
| Approved revision: | 90 | ||||||||
| Merged at revision: | 38 | ||||||||
| Proposed branch: | lp://staging/~stub/charms/precise/postgresql/old-replication | ||||||||
| Merge into: | lp://staging/charms/postgresql | ||||||||
| Prerequisite: | lp://staging/~stub/charms/precise/postgresql/old-cleanups | ||||||||
| Diff against target: |
164 lines (+57/-50) 3 files modified
README.markdown (+0/-4) TODO (+0/-12) hooks/hooks.py (+57/-34) |
||||||||
| To merge this branch: | bzr merge lp://staging/~stub/charms/precise/postgresql/old-replication | ||||||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Mark Mims (community) | Approve | ||
|
Review via email:
|
|||
Description of the change
Use pg_basebackup instead of rsync (via repmgr) to clone databases. pg_basebackup doesn't require putting the database into backup mode, which will conflict with any other process trying to make a filesystem level backup. This allows multiple hot standbys to be built simultaneously. It is not quite as efficient, but this loss should be negligable for building new replicas rather than refreshing old ones.
To post a comment you must log in.
Revision history for this message
| Stuart Bishop (stub) wrote | # |
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
Diff at http://