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

David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> On Tue, 20 Oct 2026 at 16:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So CLDR's comment is wrong, and seemingly always has been if you
>> assume it's meant to specify the zone's standard time.

> ...
> So at least the comment was correct at one point.

Ah, I failed to look closely enough. There's still room for CLDR to
fix their comments, if anyone feels like double-checking the other
zone discrepancies and filing a bug. But it's not super important
for our purposes.

Apropos of this, I just read an uber-informative post on the tz
mailing list:

https://lists.iana.org/hyperkitty/list/tz(at)iana(dot)org/message/JBMDX4TTIU4HAUSDLOKKI3JRLYJZGUEG/

So according to this apparently-very-well-informed person, TZDB is
what is under the hood in modern Windows releases, and what we are
doing in findtimezone.c is trying to map from their legacy
representation back to underlying truth. I wonder whether what we
should really be doing is burning that code to the ground and fetching
data from one of their modern APIs instead. Of course question #1 is
whether those modern APIs exist in all Windows versions we still care
to support.

regards, tom lane