We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Lobsters·Jun 22·5 min read
British Columbia, Time Zones, and Postgres
TL;DR
British Columbia's shift to year-round Pacific Daylight Savings Time creates a problem for time zone calculations in databases. PostgreSQL uses UTC timestamps for storage, which can lead to discrepancies if time zone rules change.
✦ Why It Matters
Engineers should regularly update tzdata packages to ensure accurate time zone handling in applications.
Key Takeaways
- Regularly update tzdata packages in PostgreSQL.
- Store timestamps in UTC to avoid local time discrepancies.
- Be aware of local time zone changes when querying data.
- Test time-sensitive applications after time zone updates.
Full Summary
In March 2026, British Columbia adopted a permanent UTC-7 offset by eliminating the fall back to UTC-8 for Daylight Savings Time. PostgreSQL, a popular relational database, stores timestamps in UTC format, which can lead to issues when local time zone rules change.
If a timestamp is stored using the America/Vancouver time zone, it is converted to UTC based on the rules at the time of storage. When querying that timestamp later, PostgreSQL uses the current time zone rules, which may differ from those at the time of storage.
If the tzdata package, which contains time zone information, is not updated, PostgreSQL will apply outdated rules, resulting in incorrect local times. This situation highlights the importance of regularly updating time zone data in databases to ensure accurate time calculations.
Engineers must be aware of these changes to avoid scheduling errors in applications relying on precise time data.