4 ms·

Most of the time i just use that: https://pgtune.leopard.in.ua/#/ https://pgtune.leopard.in.ua/#/

• 2mol 6y ago
  That's awesome! Do you know something similar for sane security settings?
  • nix23 6y ago
    No sorry. But for SSL security this is really nice: https://ssl-config.mozilla.org/#server=postgresql&version=12.1&config=intermediate&openssl=1.1.1d&guideline=5.6 https://ssl-config.mozilla.org/#server=postgresql&version=12...
• ar-jan 6y ago
  Do you know if the differences in recommended settings between Web Application and Desktop Application are mainly about network-related aspects (latency etc.), or more about typical access patterns of web vs desktop? I'm thinking of the configuration for a remote PostgreSQL server, to be accessed from a local desktop application over the internet.
  • taffer 6y ago
    Desktop Application assumes that the server is running on the user's workstation and is very conservative in terms of memory usage to avoid interfering with other applications. Web Application, on the other hand, assumes that the server is running on a dedicated computer and has all memory for itself.
• pingiun 6y ago
  This seems pretty cool, but it would benefit from some extra information on what it considers. And maybe links to documentation about the options your setting so you can double check.
  • nix23 6y ago
    It's just a webified version of pgtune: https://linux.die.net/man/8/pgtune https://linux.die.net/man/8/pgtune https://github.com/gregs1104/pgtune https://github.com/gregs1104/pgtune
• ahachete 6y ago
  One of the main reasons https://postgresql.conf https://postgresql.conf exists is precisely to provide as much information as possible to understand how to tune PostgreSQL's configuration. If generating a config would be as simple as filling in a form, this wouldn't make sense. 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
  • nix23 6y ago
    Hy, Unfortunately the site is unavailable: https://postgresql.conf/ https://postgresql.conf/ 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"
    • ahachete 6y ago
      But if you don't, it suggests you one. 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.
  • ahachete 6y ago
    Edit: url above is wrong, correct one is https://postgresqlco.nf https://postgresqlco.nf my brain tricked me ;)