British Columbia, time zones, and Postgres

Category: Engineering post
Status: confirmed
Sources: Crunchy Data, discussion
Summary: A Crunchy Data post uses British Columbia's plan to stop observing daylight saving time as a worked example of how Postgres handles time zones, showing why timestamptz plus named IANA zones (not fixed UTC offsets) is the correct storage choice and how tzdata updates propagate to stored values.
Why it matters: Time-zone-rule changes are a recurring source of date-math bugs; the post gives a concrete pattern for keeping Postgres correct across rule changes.