max_connections option no longer works
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql (Juju Charms Collection) |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
I deployed cs:trusty/
postgresql-
max_
max_
The values are represented in the juju get output:
max_connections:
description: |
DEPRECATED. Use extra_pg_conf. Maximum number of connections to allow to the PG database
type: int
value: 341
...
max_prepared_
description: |
DEPRECATED. Use extra_pg_conf. Maximum number of prepared two phase commit transactions, waiting to be committed. Defaults to 0. as using two phase commit without a process to monitor and resolve lost transactions is dangerous.
type: int
value: 342
But only max_prepared_
oot@node-7:~# cat /etc/postgresql
# juju # max_connections = 100 # (change requires restart)
# Note: Increasing max_connections costs ~400 bytes of shared memory per
#max_prepared_
# Note: Increasing max_prepared_
# It is not advisable to set max_prepared_
# max_locks_
max_prepared_
max_connections = 100
I got a few warnings in the juju logs:
2016-01-15 11:20:31 WARNING juju-log max_connections
2016-01-15 11:20:37 WARNING juju-log max_connections
2016-01-15 11:20:42 WARNING juju-log max_connections
2016-01-15 11:20:48 WARNING juju-log max_connections
Related branches
- Review Queue (community): Needs Fixing (automated testing)
- Andrew McLeod (community): Approve
- charmers: Pending requested
-
Diff: 54 lines (+14/-5)3 files modifiedconfig.yaml (+0/-1)
hooks/service.py (+5/-3)
tests/test_integration.py (+9/-1)
Confirmed that this is fixed with lp:charms/trusty/postgresql;revno=142.