←back to thread

Debian 13, Postgres, and the US/* time zones

(rachelbythebay.com)
283 points move-on-by | 1 comments | 12 Sep 25 02:33 UTC | HN request time: 0s | source
Show context
ggm ◴[12 Sep 25 02:48 UTC] No.45218201[source]▶
Is there a problem with ISO3166 denoted information in general or is there a specific US issue here? I would think ISO code denoted tzdata was a public good in some sense.
replies(3): >>45218844 #>>45219199 #>>45219576 #
masklinn ◴[12 Sep 25 06:27 UTC] No.45219199[source]▶
All the legacy time zones were moved out of the default zoneinfo install. It’s not a us-specific issue but the legacy US/ timezones remain in widespread use, and they stop working on Debian 13 ootb (possibly Ubuntu noble as well?).
replies(2): >>45219462 #>>45219568 #
pixelesque ◴[12 Sep 25 07:23 UTC] No.45219568[source]▶
Does anyone know why they are still in widespread use?

Config defaults somewhere still using them? Man page examples? Tutorials using them? Or just force of habit?

replies(5): >>45219671 #>>45220170 #>>45220261 #>>45220493 #>>45220793 #
rtpg ◴[12 Sep 25 07:39 UTC] No.45219671[source]▶
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?

replies(2): >>45220783 #>>45221354 #
1. magicalhippo ◴[12 Sep 25 12:21 UTC] No.45221354[source]▶
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...