←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: 0.226s | source
Show context
1oooqooq ◴[12 Sep 25 11:31 UTC] No.45221029[source]▶
love the takes on this one blog, but "I'm copying an old conf file for over 20yrs and now got this issue" is kinda weak.

American exceptionalism time zones aren't used since the 90s. even the cpus from that time are already dropped from kernel support. heck even the text encoding is gone.

replies(1): >>45221157 #
kstrauser ◴[12 Sep 25 11:55 UTC] No.45221157[source]▶
That’s unkind. I want to do the right thing in such cases, but I’m also learning about this today for the very first time. I’ve never, not once, heard that US/Pacific was a bad idea until this post. If not for this, I still wouldn’t know. I thought it and America/Los_Angeles were semantically identically and just kind of symlinks to PST8PDT or whatever.

If anything, the city TZ always felt off, like I was opting in to that specific city’s strange legal decisions or something.

replies(2): >>45221499 #>>45225808 #
1. Symbiote ◴[12 Sep 25 12:41 UTC] No.45221499[source]▶
For general user interfaces, it's for the user interface to show "US Pacific" or "UK" rather than America/Los_Angeles and Europe/London.

The timezone selector in KDE shows "Los Angeles | America/United States of America | Pacific" and "London | Europe/United Kingdom", for example.