From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Petr Jelinek <petr(at)2ndquadrant(dot)com> |
Subject: | Re: 002_types.pl fails on some timezones on windows |
Date: | 2021-09-30 23:47:08 |
Message-ID: | 3266414.1633045628@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Yes, it's been a while but IIRC Windows in the UK uses confusing
> terminology here even in user interfaces, so that in summer it appears
> to be wrong, which is annoying to anyone brought up on Eggert's
> system. The CLDR windowsZones.xml file shows this.
Oh, thanks for the pointer to CLDR! I tried re-generating our data
based on theirs, and ended up with the attached draft patch.
My notes summarizing the changes say:
Choose Europe/London for "Greenwich Standard Time"
(CLDR doesn't do this, but all their mappings for it are insane)
Alphabetize a bit better
Zone name changes:
Jerusalem Standard Time -> Israel Standard Time
Numerous Russian zones slightly renamed
Should we preserve the old spellings of the above? It's not clear
how long-obsolete the old spellings are.
Maybe politically sensitive:
Asia/Hong_Kong -> Asia/Shanghai
I think the latter has way better claim on "China Standard Time",
and CLDR agrees.
Resolve Links to underlying real zones:
Asia/Kuwait -> Asia/Riyadh
Asia/Muscat -> Asia/Dubai
Australia/Canberra -> Australia/Sydney
Canada/Atlantic -> America/Halifax
Canada/Newfoundland -> America/St_Johns
Canada/Saskatchewan -> America/Regina
US/Alaska -> America/Anchorage
US/Arizona -> America/Phoenix
US/Central -> America/Chicago
US/Eastern -> America/New_York
US/Hawaii -> Pacific/Honolulu
US/Mountain -> America/Denver
US/Pacific -> America/Los_Angeles
Just plain wrong:
US/Aleutan (misspelling of US/Aleutian, which is a link anyway)
America/Salvador does not exist; tzdb says
# There are too many Salvadors elsewhere, so use America/Bahia instead
# of America/Salvador.
Etc/UTC+12 doesn't exist in tzdb
Indiana (East) is not the regular US/Eastern zone
Asia/Baku -> Asia/Yerevan (Baku is in Azerbaijan, Yerevan is in Armenia)
Asia/Dhaka -> Asia/Almaty (Dhaka has its own zone, and it's in Bangladesh
not Astana)
Europe/Sarajevo is a link to Europe/Belgrade these days, so use Warsaw
Chisinau is in Moldova not Romania
Chetumal is in Quintana Roo, which is represented by Cancun not Mexico City
Haiti has its own zone
America/Araguaina seems to just be a mistake; use Sao_Paulo
America/Buenos_Aires for SA Eastern Standard Time is a mistake
(it has its own zone)
likewise America/Caracas for SA Western Standard Time
Africa/Harare seems to be obsoleted by Africa/Johannesburg
Karachi is in Pakistan, not Tashkent
New Windows zones:
"South Sudan Standard Time" -> Africa/Juba
"West Bank Standard Time" -> Asia/Hebron
(CLDR seem to have this replacing Gaza, but I kept that one too)
"Yukon Standard Time" -> America/Whitehorse
uncomment "W. Central Africa Standard Time" as Africa/Lagos
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
windows-timezone-map-updates.patch | text/x-diff | 14.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Champion | 2021-10-01 00:02:06 | Re: Support for NSS as a libpq TLS backend |
Previous Message | Alvaro Herrera | 2021-09-30 23:15:13 | Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?) |