Skip to content

Bump PostgreSQL max connections to 400

Grant Young requested to merge gy-bump-postgresql-max-connections into master

What does this MR do?

MR bumps default value for default['postgresql']['max_connections'] from 200 to 400.

Performance testing found a higher ceiling was required on larger environments, this is also the value used on .com.

The setting can lead to increased memory usage but a hard limit is a bad experience for users also. The approaches seen for this setting in the industry differ, Google Cloud SQL looks to be quite conservative but AWS RDS looks to be the opposite. We've been testing this value now for some time in our performance test pipelines with no issues.

Related issues

Closes #5691 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for the GitLab Chart opened
Edited by Grant Young

Merge request reports