←back to thread

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

(rachelbythebay.com)
283 points move-on-by | 6 comments | 12 Sep 25 02:33 UTC | HN request time: 0.019s | source | bottom
Show context
burnt-resistor ◴[12 Sep 25 09:01 UTC] No.45220171[source]▶
Always run production systems in the Etc/UTC timezone. This eliminates an entire class of problems while only creating minor inconveniences.
replies(5): >>45220222 #>>45220233 #>>45221046 #>>45221092 #>>45221989 #
Tepix ◴[12 Sep 25 09:11 UTC] No.45220222[source]▶
For servers, i agree 100%. For desktop systems, not so much.
replies(2): >>45220291 #>>45220354 #
kawsper ◴[12 Sep 25 09:28 UTC] No.45220354[source]▶
How else could you tell what time it is on the servers?
replies(1): >>45220482 #
1. raverbashing ◴[12 Sep 25 09:52 UTC] No.45220482{3}[source]▶
That's easy, if you're Walmart just use the TZ of your corporate HQ

(That's what I heard anyway)

replies(3): >>45221116 #>>45221160 #>>45222286 #
2. kstrauser ◴[12 Sep 25 11:47 UTC] No.45221116[source]▶
My non-Walmart startup was expanding from California to other regions many years ago, and there was some debate about whether we’d use UTC or America/Los_Angeles globally. I was part of Team Over My Dead Body.
replies(1): >>45222119 #
3. ThePowerOfFuet ◴[12 Sep 25 11:56 UTC] No.45221160[source]▶
Google's internal timestamps are in Pacific Time, too.
4. actionfromafar ◴[12 Sep 25 13:47 UTC] No.45222119[source]▶
But on which side? :)
replies(1): >>45222157 #
5. kstrauser ◴[12 Sep 25 13:50 UTC] No.45222157{3}[source]▶
There can be only one!
6. madcaptenor ◴[12 Sep 25 14:03 UTC] No.45222286[source]▶
I work for a different company headquartered in the central time zone and we also do this. On some systems.