pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Update our mapping of Windows time zone names using CLDR info. 14+ messages / 1 participants [nested] [flat]
* pgsql: Update our mapping of Windows time zone names using CLDR info. @ 2021-10-02 20:08 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-02 20:08 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names using CLDR info. This corrects a bunch of entries in win32_tzmap[], and adds a few new ones, based on the CLDR project's windowsZones.xml file. Non-cosmetic changes fall into four main categories: * Flat-out errors: US/Aleutan doesn't exist America/Salvador doesn't exist Asia/Baku is wrong for Yerevan Asia/Dhaka (Bangladesh) is wrong for Astana (Kazakhstan) Europe/Bucharest is wrong for Chisinau America/Mexico_City is wrong for Chetumal America/Buenos_Aires is wrong for Cayenne America/Caracas has its own zone, so poor fit for La Paz US/Eastern is wrong for Haiti US/Eastern is wrong for Indiana (East) Asia/Karachi is wrong for Tashkent Etc/UTC+12 doesn't exist Signs of Etc/GMT zones were backwards * Judgment calls: (These changes follow CLDR's choices, except for the first one) Use Europe/London for "Greenwich Standard Time", since that seems much more likely than Africa/Casablanca to be what people will think that zone name means. CLDR has Atlantic/Reykjavik here, but that's no better. Asia/Shanghai seems a better fit than Hong Kong for "China Standard Time". Europe/Sarajevo is now a link to Belgrade, ie "Central Europe Standard Time"; so use Warsaw for "Central European Standard Time". America/Sao_Paulo seems more representative than Araguaina for "E. South America Standard Time". Africa/Johannesburg seems more representative than Harare for "South Africa Standard Time". * New Windows zone names: "Israel Standard Time" "Kaliningrad Standard Time" "Russia Time Zone N" for various N "Singapore Standard Time" "South Sudan Standard Time" "W. Central Africa Standard Time" "West Bank Standard Time" "Yukon Standard Time" Some of these replace older spellings, but I kept the older spellings too in case our code runs on a machine with the older data. * Replace aliases (tzdb Links) with underlying city-named zones: (This tracks tzdb's longstanding practice, and reduces inconsistency with the rest of the entries, as well as with CLDR.) US/Alaska Asia/Kuwait Asia/Muscat Canada/Atlantic Australia/Canberra Canada/Saskatchewan US/Central US/Eastern US/Hawaii US/Mountain Canada/Newfoundland US/Pacific Back-patch to all supported branches, as is our usual practice for time zone data updates. Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/9b8d68cc6589814d121344f59e927a7e4506fb8c Modified Files -------------- src/bin/initdb/findtimezone.c | 157 ++++++++++++++++++++++++++++-------------- 1 file changed, 106 insertions(+), 51 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names using CLDR info. @ 2021-10-02 20:08 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-02 20:08 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names using CLDR info. This corrects a bunch of entries in win32_tzmap[], and adds a few new ones, based on the CLDR project's windowsZones.xml file. Non-cosmetic changes fall into four main categories: * Flat-out errors: US/Aleutan doesn't exist America/Salvador doesn't exist Asia/Baku is wrong for Yerevan Asia/Dhaka (Bangladesh) is wrong for Astana (Kazakhstan) Europe/Bucharest is wrong for Chisinau America/Mexico_City is wrong for Chetumal America/Buenos_Aires is wrong for Cayenne America/Caracas has its own zone, so poor fit for La Paz US/Eastern is wrong for Haiti US/Eastern is wrong for Indiana (East) Asia/Karachi is wrong for Tashkent Etc/UTC+12 doesn't exist Signs of Etc/GMT zones were backwards * Judgment calls: (These changes follow CLDR's choices, except for the first one) Use Europe/London for "Greenwich Standard Time", since that seems much more likely than Africa/Casablanca to be what people will think that zone name means. CLDR has Atlantic/Reykjavik here, but that's no better. Asia/Shanghai seems a better fit than Hong Kong for "China Standard Time". Europe/Sarajevo is now a link to Belgrade, ie "Central Europe Standard Time"; so use Warsaw for "Central European Standard Time". America/Sao_Paulo seems more representative than Araguaina for "E. South America Standard Time". Africa/Johannesburg seems more representative than Harare for "South Africa Standard Time". * New Windows zone names: "Israel Standard Time" "Kaliningrad Standard Time" "Russia Time Zone N" for various N "Singapore Standard Time" "South Sudan Standard Time" "W. Central Africa Standard Time" "West Bank Standard Time" "Yukon Standard Time" Some of these replace older spellings, but I kept the older spellings too in case our code runs on a machine with the older data. * Replace aliases (tzdb Links) with underlying city-named zones: (This tracks tzdb's longstanding practice, and reduces inconsistency with the rest of the entries, as well as with CLDR.) US/Alaska Asia/Kuwait Asia/Muscat Canada/Atlantic Australia/Canberra Canada/Saskatchewan US/Central US/Eastern US/Hawaii US/Mountain Canada/Newfoundland US/Pacific Back-patch to all supported branches, as is our usual practice for time zone data updates. Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/fa8db48791c58444ab35d6f2419074a717fbb9b7 Modified Files -------------- src/bin/initdb/findtimezone.c | 157 ++++++++++++++++++++++++++++-------------- 1 file changed, 106 insertions(+), 51 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names using CLDR info. @ 2021-10-02 20:08 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-02 20:08 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names using CLDR info. This corrects a bunch of entries in win32_tzmap[], and adds a few new ones, based on the CLDR project's windowsZones.xml file. Non-cosmetic changes fall into four main categories: * Flat-out errors: US/Aleutan doesn't exist America/Salvador doesn't exist Asia/Baku is wrong for Yerevan Asia/Dhaka (Bangladesh) is wrong for Astana (Kazakhstan) Europe/Bucharest is wrong for Chisinau America/Mexico_City is wrong for Chetumal America/Buenos_Aires is wrong for Cayenne America/Caracas has its own zone, so poor fit for La Paz US/Eastern is wrong for Haiti US/Eastern is wrong for Indiana (East) Asia/Karachi is wrong for Tashkent Etc/UTC+12 doesn't exist Signs of Etc/GMT zones were backwards * Judgment calls: (These changes follow CLDR's choices, except for the first one) Use Europe/London for "Greenwich Standard Time", since that seems much more likely than Africa/Casablanca to be what people will think that zone name means. CLDR has Atlantic/Reykjavik here, but that's no better. Asia/Shanghai seems a better fit than Hong Kong for "China Standard Time". Europe/Sarajevo is now a link to Belgrade, ie "Central Europe Standard Time"; so use Warsaw for "Central European Standard Time". America/Sao_Paulo seems more representative than Araguaina for "E. South America Standard Time". Africa/Johannesburg seems more representative than Harare for "South Africa Standard Time". * New Windows zone names: "Israel Standard Time" "Kaliningrad Standard Time" "Russia Time Zone N" for various N "Singapore Standard Time" "South Sudan Standard Time" "W. Central Africa Standard Time" "West Bank Standard Time" "Yukon Standard Time" Some of these replace older spellings, but I kept the older spellings too in case our code runs on a machine with the older data. * Replace aliases (tzdb Links) with underlying city-named zones: (This tracks tzdb's longstanding practice, and reduces inconsistency with the rest of the entries, as well as with CLDR.) US/Alaska Asia/Kuwait Asia/Muscat Canada/Atlantic Australia/Canberra Canada/Saskatchewan US/Central US/Eastern US/Hawaii US/Mountain Canada/Newfoundland US/Pacific Back-patch to all supported branches, as is our usual practice for time zone data updates. Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/9c76689de442fc5849e383cc370d0769f8196bf6 Modified Files -------------- src/bin/initdb/findtimezone.c | 157 ++++++++++++++++++++++++++++-------------- 1 file changed, 106 insertions(+), 51 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names using CLDR info. @ 2021-10-02 20:08 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-02 20:08 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names using CLDR info. This corrects a bunch of entries in win32_tzmap[], and adds a few new ones, based on the CLDR project's windowsZones.xml file. Non-cosmetic changes fall into four main categories: * Flat-out errors: US/Aleutan doesn't exist America/Salvador doesn't exist Asia/Baku is wrong for Yerevan Asia/Dhaka (Bangladesh) is wrong for Astana (Kazakhstan) Europe/Bucharest is wrong for Chisinau America/Mexico_City is wrong for Chetumal America/Buenos_Aires is wrong for Cayenne America/Caracas has its own zone, so poor fit for La Paz US/Eastern is wrong for Haiti US/Eastern is wrong for Indiana (East) Asia/Karachi is wrong for Tashkent Etc/UTC+12 doesn't exist Signs of Etc/GMT zones were backwards * Judgment calls: (These changes follow CLDR's choices, except for the first one) Use Europe/London for "Greenwich Standard Time", since that seems much more likely than Africa/Casablanca to be what people will think that zone name means. CLDR has Atlantic/Reykjavik here, but that's no better. Asia/Shanghai seems a better fit than Hong Kong for "China Standard Time". Europe/Sarajevo is now a link to Belgrade, ie "Central Europe Standard Time"; so use Warsaw for "Central European Standard Time". America/Sao_Paulo seems more representative than Araguaina for "E. South America Standard Time". Africa/Johannesburg seems more representative than Harare for "South Africa Standard Time". * New Windows zone names: "Israel Standard Time" "Kaliningrad Standard Time" "Russia Time Zone N" for various N "Singapore Standard Time" "South Sudan Standard Time" "W. Central Africa Standard Time" "West Bank Standard Time" "Yukon Standard Time" Some of these replace older spellings, but I kept the older spellings too in case our code runs on a machine with the older data. * Replace aliases (tzdb Links) with underlying city-named zones: (This tracks tzdb's longstanding practice, and reduces inconsistency with the rest of the entries, as well as with CLDR.) US/Alaska Asia/Kuwait Asia/Muscat Canada/Atlantic Australia/Canberra Canada/Saskatchewan US/Central US/Eastern US/Hawaii US/Mountain Canada/Newfoundland US/Pacific Back-patch to all supported branches, as is our usual practice for time zone data updates. Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e5b25f19b37b81cd4933abf4416858a626706291 Modified Files -------------- src/bin/initdb/findtimezone.c | 157 ++++++++++++++++++++++++++++-------------- 1 file changed, 106 insertions(+), 51 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names using CLDR info. @ 2021-10-02 20:08 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-02 20:08 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names using CLDR info. This corrects a bunch of entries in win32_tzmap[], and adds a few new ones, based on the CLDR project's windowsZones.xml file. Non-cosmetic changes fall into four main categories: * Flat-out errors: US/Aleutan doesn't exist America/Salvador doesn't exist Asia/Baku is wrong for Yerevan Asia/Dhaka (Bangladesh) is wrong for Astana (Kazakhstan) Europe/Bucharest is wrong for Chisinau America/Mexico_City is wrong for Chetumal America/Buenos_Aires is wrong for Cayenne America/Caracas has its own zone, so poor fit for La Paz US/Eastern is wrong for Haiti US/Eastern is wrong for Indiana (East) Asia/Karachi is wrong for Tashkent Etc/UTC+12 doesn't exist Signs of Etc/GMT zones were backwards * Judgment calls: (These changes follow CLDR's choices, except for the first one) Use Europe/London for "Greenwich Standard Time", since that seems much more likely than Africa/Casablanca to be what people will think that zone name means. CLDR has Atlantic/Reykjavik here, but that's no better. Asia/Shanghai seems a better fit than Hong Kong for "China Standard Time". Europe/Sarajevo is now a link to Belgrade, ie "Central Europe Standard Time"; so use Warsaw for "Central European Standard Time". America/Sao_Paulo seems more representative than Araguaina for "E. South America Standard Time". Africa/Johannesburg seems more representative than Harare for "South Africa Standard Time". * New Windows zone names: "Israel Standard Time" "Kaliningrad Standard Time" "Russia Time Zone N" for various N "Singapore Standard Time" "South Sudan Standard Time" "W. Central Africa Standard Time" "West Bank Standard Time" "Yukon Standard Time" Some of these replace older spellings, but I kept the older spellings too in case our code runs on a machine with the older data. * Replace aliases (tzdb Links) with underlying city-named zones: (This tracks tzdb's longstanding practice, and reduces inconsistency with the rest of the entries, as well as with CLDR.) US/Alaska Asia/Kuwait Asia/Muscat Canada/Atlantic Australia/Canberra Canada/Saskatchewan US/Central US/Eastern US/Hawaii US/Mountain Canada/Newfoundland US/Pacific Back-patch to all supported branches, as is our usual practice for time zone data updates. Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/9cc919b518553e5c85fa980221463f3a5e54e514 Modified Files -------------- src/bin/initdb/findtimezone.c | 157 ++++++++++++++++++++++++++++-------------- 1 file changed, 106 insertions(+), 51 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names using CLDR info. @ 2021-10-02 20:08 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-02 20:08 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names using CLDR info. This corrects a bunch of entries in win32_tzmap[], and adds a few new ones, based on the CLDR project's windowsZones.xml file. Non-cosmetic changes fall into four main categories: * Flat-out errors: US/Aleutan doesn't exist America/Salvador doesn't exist Asia/Baku is wrong for Yerevan Asia/Dhaka (Bangladesh) is wrong for Astana (Kazakhstan) Europe/Bucharest is wrong for Chisinau America/Mexico_City is wrong for Chetumal America/Buenos_Aires is wrong for Cayenne America/Caracas has its own zone, so poor fit for La Paz US/Eastern is wrong for Haiti US/Eastern is wrong for Indiana (East) Asia/Karachi is wrong for Tashkent Etc/UTC+12 doesn't exist Signs of Etc/GMT zones were backwards * Judgment calls: (These changes follow CLDR's choices, except for the first one) Use Europe/London for "Greenwich Standard Time", since that seems much more likely than Africa/Casablanca to be what people will think that zone name means. CLDR has Atlantic/Reykjavik here, but that's no better. Asia/Shanghai seems a better fit than Hong Kong for "China Standard Time". Europe/Sarajevo is now a link to Belgrade, ie "Central Europe Standard Time"; so use Warsaw for "Central European Standard Time". America/Sao_Paulo seems more representative than Araguaina for "E. South America Standard Time". Africa/Johannesburg seems more representative than Harare for "South Africa Standard Time". * New Windows zone names: "Israel Standard Time" "Kaliningrad Standard Time" "Russia Time Zone N" for various N "Singapore Standard Time" "South Sudan Standard Time" "W. Central Africa Standard Time" "West Bank Standard Time" "Yukon Standard Time" Some of these replace older spellings, but I kept the older spellings too in case our code runs on a machine with the older data. * Replace aliases (tzdb Links) with underlying city-named zones: (This tracks tzdb's longstanding practice, and reduces inconsistency with the rest of the entries, as well as with CLDR.) US/Alaska Asia/Kuwait Asia/Muscat Canada/Atlantic Australia/Canberra Canada/Saskatchewan US/Central US/Eastern US/Hawaii US/Mountain Canada/Newfoundland US/Pacific Back-patch to all supported branches, as is our usual practice for time zone data updates. Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e323630cdd3cf7a0a2579f20f8808a33be4391e6 Modified Files -------------- src/bin/initdb/findtimezone.c | 157 ++++++++++++++++++++++++++++-------------- 1 file changed, 106 insertions(+), 51 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names using CLDR info. @ 2021-10-02 20:08 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-02 20:08 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names using CLDR info. This corrects a bunch of entries in win32_tzmap[], and adds a few new ones, based on the CLDR project's windowsZones.xml file. Non-cosmetic changes fall into four main categories: * Flat-out errors: US/Aleutan doesn't exist America/Salvador doesn't exist Asia/Baku is wrong for Yerevan Asia/Dhaka (Bangladesh) is wrong for Astana (Kazakhstan) Europe/Bucharest is wrong for Chisinau America/Mexico_City is wrong for Chetumal America/Buenos_Aires is wrong for Cayenne America/Caracas has its own zone, so poor fit for La Paz US/Eastern is wrong for Haiti US/Eastern is wrong for Indiana (East) Asia/Karachi is wrong for Tashkent Etc/UTC+12 doesn't exist Signs of Etc/GMT zones were backwards * Judgment calls: (These changes follow CLDR's choices, except for the first one) Use Europe/London for "Greenwich Standard Time", since that seems much more likely than Africa/Casablanca to be what people will think that zone name means. CLDR has Atlantic/Reykjavik here, but that's no better. Asia/Shanghai seems a better fit than Hong Kong for "China Standard Time". Europe/Sarajevo is now a link to Belgrade, ie "Central Europe Standard Time"; so use Warsaw for "Central European Standard Time". America/Sao_Paulo seems more representative than Araguaina for "E. South America Standard Time". Africa/Johannesburg seems more representative than Harare for "South Africa Standard Time". * New Windows zone names: "Israel Standard Time" "Kaliningrad Standard Time" "Russia Time Zone N" for various N "Singapore Standard Time" "South Sudan Standard Time" "W. Central Africa Standard Time" "West Bank Standard Time" "Yukon Standard Time" Some of these replace older spellings, but I kept the older spellings too in case our code runs on a machine with the older data. * Replace aliases (tzdb Links) with underlying city-named zones: (This tracks tzdb's longstanding practice, and reduces inconsistency with the rest of the entries, as well as with CLDR.) US/Alaska Asia/Kuwait Asia/Muscat Canada/Atlantic Australia/Canberra Canada/Saskatchewan US/Central US/Eastern US/Hawaii US/Mountain Canada/Newfoundland US/Pacific Back-patch to all supported branches, as is our usual practice for time zone data updates. Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL9_6_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/dbec5a2fea4d5d6a52136dd169b0abe5b68fe1ec Modified Files -------------- src/bin/initdb/findtimezone.c | 157 ++++++++++++++++++++++++++++-------------- 1 file changed, 106 insertions(+), 51 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names some more. @ 2021-10-04 18:53 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-04 18:53 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names some more. Per discussion, let's just follow CLDR's default zone mappings faithfully. There are two changes here that are clear improvements: * Mapping "Greenwich Standard Time" to Atlantic/Reykjavik is actually a better fit than using London, because Iceland hasn't observed DST since 1968, so this is more nearly what people might expect. * Since the "Samoa" zone is specified to be UTC+13:00, we must map it to Pacific/Apia not Pacific/Samoa; the latter refers to American Samoa which is now on the other side of the date line. The rest of these changes look like they're choosing the most populous IANA zone as representative. Whatever the details, we're just going to say "if you don't like this mapping, complain to CLDR". Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/c1aa3b3c0d2125cb04df8ed0387448d8aeb9519c Modified Files -------------- src/bin/initdb/findtimezone.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names some more. @ 2021-10-04 18:53 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-04 18:53 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names some more. Per discussion, let's just follow CLDR's default zone mappings faithfully. There are two changes here that are clear improvements: * Mapping "Greenwich Standard Time" to Atlantic/Reykjavik is actually a better fit than using London, because Iceland hasn't observed DST since 1968, so this is more nearly what people might expect. * Since the "Samoa" zone is specified to be UTC+13:00, we must map it to Pacific/Apia not Pacific/Samoa; the latter refers to American Samoa which is now on the other side of the date line. The rest of these changes look like they're choosing the most populous IANA zone as representative. Whatever the details, we're just going to say "if you don't like this mapping, complain to CLDR". Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/919c08d909f766bb51c5c617714364a91bb90d9d Modified Files -------------- src/bin/initdb/findtimezone.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names some more. @ 2021-10-04 18:53 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-04 18:53 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names some more. Per discussion, let's just follow CLDR's default zone mappings faithfully. There are two changes here that are clear improvements: * Mapping "Greenwich Standard Time" to Atlantic/Reykjavik is actually a better fit than using London, because Iceland hasn't observed DST since 1968, so this is more nearly what people might expect. * Since the "Samoa" zone is specified to be UTC+13:00, we must map it to Pacific/Apia not Pacific/Samoa; the latter refers to American Samoa which is now on the other side of the date line. The rest of these changes look like they're choosing the most populous IANA zone as representative. Whatever the details, we're just going to say "if you don't like this mapping, complain to CLDR". Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/c53ff69e1fd24ae4905fe50ce8d3ca3a08d6a3c2 Modified Files -------------- src/bin/initdb/findtimezone.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names some more. @ 2021-10-04 18:53 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-04 18:53 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names some more. Per discussion, let's just follow CLDR's default zone mappings faithfully. There are two changes here that are clear improvements: * Mapping "Greenwich Standard Time" to Atlantic/Reykjavik is actually a better fit than using London, because Iceland hasn't observed DST since 1968, so this is more nearly what people might expect. * Since the "Samoa" zone is specified to be UTC+13:00, we must map it to Pacific/Apia not Pacific/Samoa; the latter refers to American Samoa which is now on the other side of the date line. The rest of these changes look like they're choosing the most populous IANA zone as representative. Whatever the details, we're just going to say "if you don't like this mapping, complain to CLDR". Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/07873a5dc925059fc76ddfd81db9a545faf06d33 Modified Files -------------- src/bin/initdb/findtimezone.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names some more. @ 2021-10-04 18:53 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-04 18:53 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names some more. Per discussion, let's just follow CLDR's default zone mappings faithfully. There are two changes here that are clear improvements: * Mapping "Greenwich Standard Time" to Atlantic/Reykjavik is actually a better fit than using London, because Iceland hasn't observed DST since 1968, so this is more nearly what people might expect. * Since the "Samoa" zone is specified to be UTC+13:00, we must map it to Pacific/Apia not Pacific/Samoa; the latter refers to American Samoa which is now on the other side of the date line. The rest of these changes look like they're choosing the most populous IANA zone as representative. Whatever the details, we're just going to say "if you don't like this mapping, complain to CLDR". Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/d0b0b70dc2a60d68f97af5264fe432e245eea3a5 Modified Files -------------- src/bin/initdb/findtimezone.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names some more. @ 2021-10-04 18:53 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-04 18:53 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names some more. Per discussion, let's just follow CLDR's default zone mappings faithfully. There are two changes here that are clear improvements: * Mapping "Greenwich Standard Time" to Atlantic/Reykjavik is actually a better fit than using London, because Iceland hasn't observed DST since 1968, so this is more nearly what people might expect. * Since the "Samoa" zone is specified to be UTC+13:00, we must map it to Pacific/Apia not Pacific/Samoa; the latter refers to American Samoa which is now on the other side of the date line. The rest of these changes look like they're choosing the most populous IANA zone as representative. Whatever the details, we're just going to say "if you don't like this mapping, complain to CLDR". Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/cd24791425882a76e890743728f381b7f764cf29 Modified Files -------------- src/bin/initdb/findtimezone.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
* pgsql: Update our mapping of Windows time zone names some more. @ 2021-10-04 18:53 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 14+ messages in thread From: Tom Lane @ 2021-10-04 18:53 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Update our mapping of Windows time zone names some more. Per discussion, let's just follow CLDR's default zone mappings faithfully. There are two changes here that are clear improvements: * Mapping "Greenwich Standard Time" to Atlantic/Reykjavik is actually a better fit than using London, because Iceland hasn't observed DST since 1968, so this is more nearly what people might expect. * Since the "Samoa" zone is specified to be UTC+13:00, we must map it to Pacific/Apia not Pacific/Samoa; the latter refers to American Samoa which is now on the other side of the date line. The rest of these changes look like they're choosing the most populous IANA zone as representative. Whatever the details, we're just going to say "if you don't like this mapping, complain to CLDR". Discussion: https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us Branch ------ REL9_6_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b5f34ae08ad2153f66d2463ad008da9e67ec6b03 Modified Files -------------- src/bin/initdb/findtimezone.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) ^ permalink raw reply [nested|flat] 14+ messages in thread
end of thread, other threads:[~2021-10-04 18:53 UTC | newest] Thread overview: 14+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-10-02 20:08 pgsql: Update our mapping of Windows time zone names using CLDR info. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-02 20:08 pgsql: Update our mapping of Windows time zone names using CLDR info. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-02 20:08 pgsql: Update our mapping of Windows time zone names using CLDR info. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-02 20:08 pgsql: Update our mapping of Windows time zone names using CLDR info. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-02 20:08 pgsql: Update our mapping of Windows time zone names using CLDR info. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-02 20:08 pgsql: Update our mapping of Windows time zone names using CLDR info. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-02 20:08 pgsql: Update our mapping of Windows time zone names using CLDR info. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-04 18:53 pgsql: Update our mapping of Windows time zone names some more. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-04 18:53 pgsql: Update our mapping of Windows time zone names some more. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-04 18:53 pgsql: Update our mapping of Windows time zone names some more. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-04 18:53 pgsql: Update our mapping of Windows time zone names some more. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-04 18:53 pgsql: Update our mapping of Windows time zone names some more. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-04 18:53 pgsql: Update our mapping of Windows time zone names some more. Tom Lane <tgl@sss.pgh.pa.us> 2021-10-04 18:53 pgsql: Update our mapping of Windows time zone names some more. Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox