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

Abierto
  • ¿Algo no está bien?
#2,591 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
postgresql
Área
databases

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Nix
Estrellas
1.8k
Forks
272
Merge medio
4 d 4 h
PR fusionados (30 d)
62

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de supabase/postgres

Todos los issues de supabase/postgres

Issues similares

Más issues de Databases

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.