British Colombia, Time Zones, and Postgres
winslett
11 points
1 comment
June 16, 2026
Related Discussions
Found 5 related stories in 104.8ms across 10,715 title embeddings via pgvector HNSW
- British Columbia is permanently adopting daylight time ireflect · 638 pts · March 02, 2026 · 58% similar
- The surprising whimsy of the Time Zone Database jprs · 79 pts · March 07, 2026 · 51% similar
- BC got rid of Daylight Savings mostelato · 27 pts · March 10, 2026 · 48% similar
- Postgres Traffic Control samlambert · 17 pts · March 23, 2026 · 45% similar
- Postgres by Example thenewedrock · 46 pts · June 10, 2026 · 44% similar
Discussion Highlights (1 comments)
Ndymium
The naming of "timestamp with time zone" is one of my favorite pet peeves. It's one of those things that you can say "well technically it's true" about. The article suggests that for past events, UTC and this timestamptz would be acceptable as a general rule, but even there it depends on what you will be doing with the data. If you intend to interpret it as a series of local occurrences and try to visualize/summarize that data later, you may be in for a surprise as your user has moved to another timezone and now all the past events are translated to the wrong local hours [0]. For example, your system might end up showing that the user's best time for jogging based on historical data is at 2 in the night. [0] https://blog.nytsoi.net/2022/03/13/utc/