Skip to content
FIRERUN.

The BaaS & deploy-platform newsroom for builders

Subscribe

Supabase

Supabase Postgres Returns the Wrong Hour for Vancouver and Edmonton

Check your Postgres version, upgrade and reindex any time zone expression index. Older Supabase builds get Vancouver and Edmonton time wrong.

Hand-drawn editorial illustration for "Supabase Postgres Returns the Wrong Hour for Vancouver and Edmonton"

Supabase projects on older Postgres builds convert timestamps to the wrong local time for Vancouver, Edmonton and Casablanca, and they do it without raising an error. Since Nov. 1, any query that uses AT TIME ZONE 'America/Vancouver' or 'America/Edmonton' on an affected project returns a time one hour off. Supabase said the fix is an upgrade to Postgres 15.19.0.003 or 17.11.0.003, which causes downtime (Supabase changelog, Oct. 2026).

What Broke

Postgres reads time zone rules from the tzdata package. Supabase said in its Oct. 30 changelog that older images ship an outdated copy, so three zones that changed their rules in 2026 come out wrong:

  • British Columbia (America/Vancouver), which changed on March 8
  • Morocco (Africa/Casablanca), which changed on Sept. 20
  • Alberta (America/Edmonton), which changed on Nov. 1

The changes are moves to permanent time. The IANA time zone database’s 2026c release, published in July, moved Alberta to a permanent UTC-6 and Morocco to a permanent UTC+0; the earlier 2026b release put British Columbia on a permanent UTC-7. IANA said it modeled Alberta’s switch to take effect Nov. 1 at 2 a.m., matching how it handled British Columbia, though Alberta’s legal change came in June.

That makes Nov. 1 the day the bug showed up. A database with the old rules fell back an hour that night for both Canadian provinces, which kept their clocks where they were.

Supabase said stored data and timestamps are intact. Only the conversion to local time is wrong.

How to Check and Fix It

Supabase’s troubleshooting guide gives the steps:

  1. Open Project Settings > General and read Service Version. Anything below 15.19.0.003 or 17.11.0.003 is affected if it uses one of the three zones.
  2. Or run select now() at time zone 'America/Vancouver'; and compare it with a wall clock.
  3. Upgrade from the same settings page during a low-traffic window, because the upgrade takes the database down.
  4. Rebuild any index whose definition converts to an affected zone, such as ((col AT TIME ZONE 'America/Vancouver')::date). Find them by searching pg_indexes for at time zone or the zone names, then run reindex index concurrently on each.

Indexes on plain timestamptz columns don’t need a rebuild, Supabase said. If the expression indexes are skipped, queries that use them keep returning results computed with the old rules.

The Take

A silent off-by-one-hour is worse than a crash. Nobody gets paged. A booking app in Calgary shows 9 a.m. slots as 8 a.m., a daily report built on a local-date index rolls over at 1 a.m., and the first person to notice is a customer.

Teams are most likely to skip the index rebuild. An upgrade fixes new conversions, but an expression index keeps the stale answers it already computed, so a query can still read the old hour after the version number looks right. Run the pg_indexes search before closing the ticket.

The exposure reaches past Western Canada and Morocco. Any app with users in those places that renders times in the database, such as reminders or jobs keyed to local midnight, is affected. Apps that store UTC and convert in the client rely on the browser’s time zone data instead of whatever tzdata a hosted Postgres image carries.

Stay in the loop

Get new articles in your inbox

We'll only email you when a new article drops. Unsubscribe anytime.