Only default port supported

Bug #1130577 reported by Stuart Bishop
6
This bug affects 1 person
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

Revision history for this message
Stuart Bishop (stub) wrote :

port is being published.

Changing the config value still breaks things though, as there are serveral places the default port of 5432 is hardcoded.

Changed in postgresql (Juju Charms Collection):
status: New → Confirmed
status: Confirmed → New
Revision history for this message
Stuart Bishop (stub) wrote :

I think using a different port in the charm would be fairly easy, but testing that it actually does this not so easy.

Revisit after we have better test support from juju, if anyone actually has a use case.

Changed in postgresql (Juju Charms Collection):
status: New → Won't Fix
Stuart Bishop (stub)
Changed in postgresql (Juju Charms Collection):
status: Won't Fix → In Progress
importance: Undecided → Low
assignee: nobody → Stuart Bishop (stub)
Stuart Bishop (stub)
Changed in postgresql (Juju Charms Collection):
status: In Progress → 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.