Some of this is surely just muscle memory or intertia as well. I remember random config values from when I was trying out linux boxes back in high school that I replicated into files that just don't get touched for decades afterwards.

When was the last time you rebuilt your company's postgres config from scratch?

▲

Symbiote 4 days ago | parent | next [-]

> When was the last time you rebuilt your company's postgres config from scratch?

Last year, when we upgrade to version 17.

I looked at the example/template configuration, diffed it with our configuration from PG15, and for every change decided whether to keep our version or the new setting.

I didn't use it, but Debian/APT has had a tool to do this sort of comparison for any software upgrade for as long as I can remember.

Do other people just copy the old config and shout "YOLO!"?

	▲	rtpg a day ago \| parent [-]
		When your configuration value from PG15 was different from the old default and the new default on something like the statement timeout, and the statement timeout was previously working fine, and obstensibly set for a reason.... I dunno, are you going to question the value that much? And you might say "well I know how a statement timeout works" and I agree! I would also generally agree that something like a timezone setting would generally be something I'd expect to be fairly stable. That's what I meant about rebuilding the config from scratch. Rebuilding from scratch would almost involve _not even looking at the existing configuration_ and then doing first principles footwork to figure out what is needed. I think the diffing flow you went through is the right way to do it, but I believe that flow might lead to some values getting less scrutiny than others. Still perfectly reasonable though

▲

magicalhippo 4 days ago | parent | prev [-]

Still typing "nano -w filename" each and every time since back around y2k when I was working on Linux for the first time I was told that bad things could happen if I didn't...