Re: BUG #18455: DST information is flagged wrongly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: gkchinna(dot)oracle(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18455: DST information is flagged wrongly
Date: 2024-05-02 16:42:25
Message-ID: 2241008.1714668145@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> Ah ... having now refreshed my memory, the answer is that RHEL
> and Apple are distributing "rearguard" tzdata files, whereas
> ours are built with the main ("vanguard") data model.

Further to that ... on recent Fedora I get

$ zdump -v Europe/Dublin | grep 2024
Europe/Dublin Sun Mar 31 00:59:59 2024 UT = Sun Mar 31 00:59:59 2024 GMT isdst=1 gmtoff=0
Europe/Dublin Sun Mar 31 01:00:00 2024 UT = Sun Mar 31 02:00:00 2024 IST isdst=0 gmtoff=3600
Europe/Dublin Sun Oct 27 00:59:59 2024 UT = Sun Oct 27 01:59:59 2024 IST isdst=0 gmtoff=3600
Europe/Dublin Sun Oct 27 01:00:00 2024 UT = Sun Oct 27 01:00:00 2024 GMT isdst=1 gmtoff=0

So Red Hat is indeed moving in the direction of adopting the vanguard
data; they just haven't pulled that trigger yet in RHEL.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2024-05-02 16:52:05 Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune()
Previous Message Tom Lane 2024-05-02 16:12:22 Re: BUG #18455: DST information is flagged wrongly