Show HN: Postgresqlco.nf: PostgreSQL Configuration for Humans

Re:Show HN: Postgresqlco.nf: PostgreSQL Configuration for Hu... by adwf on Friday January 24, 2020 @02:47PM (#22141788)

I wouldn't say that postgres is hard to tune. Yes it has ~300 parameters in a config file, but a lot of those are to do with logging/admin etc.

There are about 6 parameters that I might touch on every deployment:

Listen address, shared buffers (default it to 25% RAM), connection counts, max workers (CPU core count), max parallel workers and max WAL keep segments.

That's 95% of the tuning you need on an average deployment. The rest is a bit dependent on workload (like checkpoint timeouts on heavy-write boxes).

EDIT: And when I say "need", the actual defaults out of the box will usually get you a long way. Just set the right listen address and let it do its thing.

[ Parent | on HN ]

Re:Show HN: Postgresqlco.nf: PostgreSQL Configuration for Hu... by RobertRoberts on Friday January 24, 2020 @03:59PM (#22142401)

Thanks. Without a lot of time invested it's hard to figure this out on your own, I appreciate this summary.

The comments here have bolstered my resolve to move to Postgres. :)

[ Parent | on HN ]