Postgres max_prepared_transactions to the same value as max_connections for landscape

[Mihaela Andronic]

Hi,

The landscape Charm doesn't seem to take care of the values for max_prepared_transactions and max_connections. The Official recommendation for the set up is to have these 2 settings to the same value https://help.landscape.canonical.com/LDS/ManualInstallation17.03 ex:

> max_connections = 400
> ...
> max_prepared_transactions = 400

From looking at the most recent code for landscape there is no setting to check and enforce or recommend this for the PostgreSQL set-up.

From what I can tell of the last charm version (Postgresql #164) these parameters are also deprecated https://jujucharms.com/postgresql/

> "max_connections":
> "default": !!int "100"
> "type": "int"
> "description": "DEPRECATED. Use extra_pg_conf."
> "max_prepared_transactions":
> "default": !!int "0"
> "type": "int"
> "description": "DEPRECATED. Use extra_pg_conf."

https://api.jujucharms.com/charmstore/v5/postgresql/archive/config.yaml ^

Is there a plan for keeping these requested parameters in sync for the charm? Is there a reason the charm does not set it?

Thank you

[Stuart Bishop (stub)]

The charm can certainly default these to the same value, and allow it to be overridden if explicitly added to the config.