3 ms·
I never made any changes to Postgres for development and it was blazing fast. I made few simple changes for production to let it use more memory (just few lines
by vbezhenar 7y ago
I never made any changes to Postgres for development and it was blazing fast. I made few simple changes for production to let it use more memory (just few lines that you'll find in any guide) and that was about it. I guess, there are plenty of handles for very pro users when they need to squeeze last few percents of performance, but generally it just works fast.
- RobertRoberts 7y agoThanks, that is what I was hoping for.
- topspin 7y agoThis site is actually misleading in my opinion; someone with no prior exposure might think postgresql users are obligated to spend their time in endless configuration push ups. That is definitely not the case. As the parent points out, developers rarely have to change more than a few things. Production means real loads and real loads drive administrators to configure and tune, but that's as true for MySQL/MariaDB as it is for Postgresql. Over here[1] you can read about the 1163 snake cased MariaDB variables if you want... 231 of them are specific to innodb alone. [1] https://mariadb.com/kb/en/server-system-variables/ https://mariadb.com/kb/en/server-system-variables/