---
slug: tzdata-local-time-vancouver-edmonton-casablanca
published: 2026-10-30
change_type: bug-fix
affected_products:
  - Database
page: https://supabase.com/changelog/tzdata-local-time-vancouver-edmonton-casablanca
---

# Upgrade Postgres to fix local time for Vancouver, Edmonton, and Casablanca

Some older Supabase Postgres versions ship an outdated `tzdata` package. As a result, local-time conversions such as `AT TIME ZONE 'America/Vancouver'` return incorrect results for three zones that changed their rules in 2026:

- British Columbia, Canada (`America/Vancouver`): changed on March 8, 2026.
- Morocco (`Africa/Casablanca`): changed on September 20, 2026.
- Alberta, Canada (`America/Edmonton`): changes on November 1, 2026.

This issue affects projects that use one of these zones and run a version earlier than 15.19.0.003 (Postgres 15) or 17.11.0.003 (Postgres 17). Versions 15.19.0.003 and 17.11.0.003 include the updated `tzdata` package.

Your stored data and timestamps are not affected. Only the conversion to local time for these zones is wrong.

### How to check and fix your projects

You can find your version under **Service Version** in [Project Settings > General](https://supabase.com/dashboard/project/_/settings/general) and upgrade from there to get the fix. The upgrade causes downtime, so plan it for a low-traffic window. Some indexes might need a rebuild after the upgrade.

For full instructions, refer to [Wrong local time for Vancouver, Edmonton, and Casablanca time zones](https://supabase.com/docs/guides/troubleshooting/wrong-local-time-for-vancouver-edmonton-casablanca-time-zones).