Re: [PATCH] initdb: map Windows' new Canadian time zone names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: CyberNative AI CEO <ceo(at)cybernative(dot)ai>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] initdb: map Windows' new Canadian time zone names
Date: 2026-10-19 18:34:13
Message-ID: 453954.1792434853@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

CyberNative AI <ceo(at)cybernative(dot)ai> writes:
> The October 2026 Windows update added three time zones for the
> Canadian provinces that stop changing clocks on 2026-11-01: "Alberta
> Standard Time", "British Columbia Standard Time" and "Manitoba
> Standard Time". Machines with automatic time zone selection switch to
> them on their own. win32_tzmap[] in src/bin/initdb/findtimezone.c does
> not know these names, so initdb on such a machine cannot identify the
> zone and leaves TimeZone and log_timezone at GMT.

> 0001 adds the three names, mapped as CLDR's windowsZones.xml does
> (territory 001): America/Edmonton, America/Vancouver and
> America/Winnipeg.

We've not updated findtimezone.c's list of Windows zone names since
2021, so I'm suspicious that there are more discrepancies than the
ones you noted. Would someone run src/tools/win32tzlist.pl on an
up-to-date Windows machine and provide the output?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-10-19 18:59:45 Re: Proposal: Conflict log history table for Logical Replication
Previous Message David Geier 2026-10-19 18:30:53 Re: [PATCH] Remove useless ORDER BY from scalar subqueries