Postgres max_prepared_transactions to the same value as max_connections for landscape
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Charm |
New
|
Undecided
|
Unassigned | ||
PostgreSQL Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
Hi,
The landscape Charm doesn't seem to take care of the values for max_prepared_
> max_connections = 400
> ...
> max_prepared_
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:/
> "max_connections":
> "default": !!int "100"
> "type": "int"
> "description": "DEPRECATED. Use extra_pg_conf."
> "max_prepared_
> "default": !!int "0"
> "type": "int"
> "description": "DEPRECATED. Use extra_pg_conf."
https:/
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
summary: |
Postgres max_prepared_transactions to the same value as max_connections - for landcape + for landscape |
The charm can certainly default these to the same value, and allow it to be overridden if explicitly added to the config.