Postgres max_prepared_transactions to the same value as max_connections for landscape

Bug #1738780 reported by Mihaela Andronic
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Charm
PostgreSQL Charm

Bug Description


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 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

> "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." ^

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
Revision history for this message
Stuart Bishop (stub) wrote :

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

Changed in postgresql-charm:
status: New → Triaged
importance: Undecided → Medium
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.