Most of the time i just use that:
It's tempting to think it may be a good starting point. Unfortunately, it might as well be a bad starting point: form-based configurations may be totally counter-productive. For instance, max_connections is a parameter that may cause outages or very bad performance if not properly configured. And its value depends, if anything, on having or not a connection pool. work_mem heavily depends on the types of queries that you run. Plus I disagree with some of the other choices made by pgtune's default behaviour.
All in all, I'd recommend to do a deeper study of the parameters, or seek some expert help, specially for production environments.
Disclaimer: I'm part of the team behind postgresql.conf
Unfortunately the site is unavailable:
I never wrote it's a brainless goto conf generator.
>max_connections is a parameter that may cause outages or very bad performance if not properly configured.
That's why you can define the "Number of Connections"
My point here is that some of the suggestions provided, if taken by a non expert user, may do more harm than good. And the reason is that there are many factors that need to be considered for most of the parameters. Something it's hard to capture from a form-based configuration generation tool.
That's why my recommendation of not using form-based configuration generation tools. They can be counter-productive.
https://ssl-config.mozilla.org/#server=postgresql&version=12...