Our RDS database uses America/Denver, and I'm concerned about daylight-saving changes causing a mismatch with Alberta time. What should we set it to?
What timezone should I use for RDS in Alberta?
Answers
I'd use UTC for the database and backend, then convert to the relevant local timezone when showing times to users. That gives you a consistent reference for stored timestamps and avoids tying the database clock to daylight-saving changes.
For Alberta local time, use America/Edmonton for the conversion rather than a fixed UTC offset. That lets timezone rules account for seasonal changes.
Reply to this answer
Before changing the RDS setting, check the database engine and how the application writes and reads timestamps. A timezone setting doesn't necessarily convert existing values, and changing it could alter how timezone-less dates are interpreted or displayed.
Test the change with sample dates on both sides of a clock transition. Keep UTC as the storage convention for moments in time, but preserve the relevant local timezone when the business meaning depends on local clock time.
Reply to this answer
If the immediate concern is Denver versus Alberta, compare their offsets on the actual dates you're worried about. Don't pick a fixed offset just to avoid a clock change. A named timezone carries the rules needed for local-time conversion.
Reply to this answer
Add your answer
Answers are reviewed before publication.
r.859!cloverladle:
Alberta generally observes daylight saving time, so it is worth checking the date and timezone rules before assuming its clocks won't change.