Merge lp://staging/~ahasenack/charms/precise/postgresql/use-postgres-instead-of-template1 into lp://staging/charms/postgresql
Proposed by
Andreas Hasenack
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merged at revision: | 83 | ||||
| Proposed branch: | lp://staging/~ahasenack/charms/precise/postgresql/use-postgres-instead-of-template1 | ||||
| Merge into: | lp://staging/charms/postgresql | ||||
| Diff against target: |
20 lines (+2/-2) 1 file modified
hooks/hooks.py (+2/-2) |
||||
| To merge this branch: | bzr merge lp://staging/~ahasenack/charms/precise/postgresql/use-postgres-instead-of-template1 | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Stuart Bishop (community) | Approve | ||
|
Review via email:
|
|||
Commit message
Use the postgres database instead of template1 so we don't block database creation by others.
Description of the change
Use the postgres database instead of template1 so we don't block database creation by others.
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
As discussed on IRC, the reason for this change is that createdb uses template1 by default as its template database. If there are connections to the template database, and they can hang around for a few moments on the server after being closed by the client, the createdb will fail.
The simplest solutions are to either not open connections to the template database, or use template0 as the createdb template database. This fix does the former.