America/Winnipeg still converts with pre-2026e rules in 17.11.0.x; Manitoba's permanent UTC−5 starts 2026-11-01

Aperta
  • Qualcosa non va?
#2,591 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
postgresql
Ambito
databases

Direzione di ricerca

The report identifies the embedded timezone data at src/timezone/data/tzdata.zi and reproduces the issue with America/Winnipeg in a SQL query. Start by checking how the image build packages PostgreSQL's timezone data and compare its rules with tzdata 2026e. Done means the reported query returns 2026-11-02 17:00:00+00 and the issue names the image version carrying the update.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Follow-up to #2465, which #2501 closed by moving the build to PostgreSQL's embedded tzdata.

That embedded data is 2026c. IANA tzdata 2026e (released 2026-09-29) moves Manitoba to permanent UTC−5 on
2026-10-31, modelled from 2026-11-01 02:00 local, so every current image still applies the old fall-back to
UTC−6 for America/Winnipeg. (The 2026-10-08 comment on #2465 flagged this class of gap.)

Repro, on any image or project:

select ('2026-11-02 12:00'::timestamp at time zone 'America/Winnipeg')::text;
  • Got: 2026-11-02 18:00:00+00 on public.ecr.aws/supabase/postgres 17.6.1.143, 17.11.0.004 and
    17.11.0.007 (newest tag as of 2026-10-22).
  • Expected with tzdata ≥ 2026e: 2026-11-02 17:00:00+00.

Upgrading to 17.11.0.003 or later, as the 2026-10-09 reply on #2465 suggests, does not fix this: both 17.11 tags
above are later and still answer 18:00.

Impact: from 2026-11-01, every Winnipeg wall-clock time that Postgres converts is an hour off from clients
on current rules (Node ≥ 24.22.1 ships 2026e, and OS and browser updates are rolling out). A scheduling app
computes lesson slots in the database and displays them on the device, so the two disagree by an hour.
PostgreSQL's next minor releases are scheduled for 2026-11-12, after the change.

Ask: ship tzdata 2026e in the images and on hosted projects before 2026-11-01, for example by patching the
embedded src/timezone/data/tzdata.zi or building against a current system tzdata again. Please also say which
image version carries it.

Lingua principale
Nix
Stelle
1.8k
Fork
272
Merge medio
4g 4h
PR unite (30g)
62

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di supabase/postgres

Tutte le issue di supabase/postgres

Issue simili

Altre issue su Databases

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.