Hacker News new | ask | show | jobs
by dewey 2653 days ago
> It is probably more valuable than this blog post.

Learning about what goes on under the hood before you blindly change settings some tool spits out doesn't seem like a bad idea I'd say.

2 comments

The point is that the pgtune could and should force you to check the config options in documentation and it actually addresses your current setup. RTFM.

Values in the post are pretty arbitrary and useless as their comments in postgresql.conf used to be.

I am using PostgreSQL in production since 7.4 and the best source of performance tuning tips for me has been PostgreSQL 9.0 High Performance by Gregory Smith. These days PostgreSQL wiki is pretty good as well.

I'd second that book recommendation. I just went through it again on a long plane flight, and much (if not all) of the configuration advice applies to more recent releases as well.
For sure. And although I love pgtune and it's usually my first stop when I'm firing up a new database, it's only really modifying a few parameters when there's a whole host of server configuration tweaks available:

https://www.postgresql.org/docs/current/runtime-config.html