listen_port is NoneType
Bug #1313719 reported by
Marco Ceppi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| postgresql (Juju Charms Collection) |
Expired
|
Medium
|
Unassigned | ||
Bug Description
The default port is NoneType, which then incurs some extra programmatic logic to set it in the hooks. It would be simpler and more compelling for a user, if the default value was what a NoneType value for that config option equated to. In the upcoming proof changes NoneType's will be supported for Strings but not integers, so this will continue to violate proof after that change lands
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in postgresql (Juju Charms Collection): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Stuart Bishop (stub) wrote | #2 |
| Changed in postgresql (Juju Charms Collection): | |
| status: | Confirmed → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in postgresql (Juju Charms Collection): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
The default port is chosen when the PostgreSQL cluster is created - it will normally be 5432 but a higher one will be chosen if 5432 is already in use by another PostgreSQL cluster.
I'm tempted to remove the option entirely rather than hack it to use '-1' or similar as a substitute to NULL/None/null. The option only started actually working recently, and I still can't think of any compelling use case for users to specify the port number.