Only default port supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql (Juju Charms Collection) |
Fix Released
|
Low
|
Stuart Bishop |
Bug Description
The PostgreSQL charm allows you to specify the port PostgreSQL will listen on. However, this information is not published to related clients making it useless.
Dropping support for a custom port is the easiest fix. It is only useful when co-hosting charms in a single container, and we cannot support multiple PostgreSQL charms per container due to PostgreSQL tablespaces using absolute paths. Co-hosting a connection pool like pgbouncer with PostgreSQL is a valid use case.
Alternatively, we can publish the port information on all the relationships. Existing charms will need to be updated to use this information, as will the master, slave and replication relationship hooks in the PostgreSQL charm.
Related branches
- Marco Ceppi (community): Approve
-
Diff: 1315 lines (+538/-184)19 files modified.bzrignore (+3/-0)
Makefile (+20/-3)
README.md (+6/-3)
config.yaml (+38/-15)
hooks/charmhelpers/fetch/__init__.py (+2/-2)
hooks/hooks.py (+283/-132)
lib/ACCC4CF8.asc (+45/-0)
templates/pg_hba.conf.tmpl (+1/-1)
templates/pg_ident.conf.tmpl (+1/-0)
templates/postgresql.conf.tmpl (+5/-0)
templates/recovery.conf.tmpl (+1/-1)
test.py (+91/-21)
testing/jujufixture.py (+17/-5)
tests/00_setup.test (+12/-0)
tests/01_lint.test (+3/-0)
tests/02_unit_test.test (+1/-1)
tests/91_integration_test_91.test (+3/-0)
tests/92_integration_test_92.test (+3/-0)
tests/93_integration_test_93.test (+3/-0)
Changed in postgresql (Juju Charms Collection): | |
status: | Won't Fix → In Progress |
importance: | Undecided → Low |
assignee: | nobody → Stuart Bishop (stub) |
Changed in postgresql (Juju Charms Collection): | |
status: | In Progress → Fix Released |
port is being published.
Changing the config value still breaks things though, as there are serveral places the default port of 5432 is hardcoded.