| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | CyberNative AI CEO <ceo(at)cybernative(dot)ai>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] initdb: map Windows' new Canadian time zone names |
| Date: | 2026-10-20 03:48:38 |
| Message-ID: | CAApHDvo_VYtc1aZ1XUYszF=6hFodKNrbn1sTaxp-GKh6OS25jA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. But I don't
> regard that as our bug to fix, especially since it's only a comment
> so far as our code is concerned. Perhaps somebody more excited
> about this than me will file a bug report with CLDR about these.
Going by [1], there was a brief stint in UTC+4 for 2 years from Oct 2018:
postgres=# select '2019-07-01 00:00:00 UTC' at time zone 'Europe/Volgograd';
timezone
---------------------
2019-07-01 04:00:00
(1 row)
So at least the comment was correct at one point.
David
[1] https://www.timeanddate.com/news/time/russia-volgograd-time-zone.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manu | 2026-10-20 03:52:06 | Re: ZSTD TOAST compression, and an extensible compression method encoding |
| Previous Message | Tom Lane | 2026-10-20 03:44:03 | Re: [PATCH] initdb: map Windows' new Canadian time zone names |