From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: tzdata 2025b |
Date: | 2025-03-31 23:09:57 |
Message-ID: | CAD21AoDr-nXm-7MtamG2fPYsS1ZkD4DvOBp2HNHLk5--7DDz6g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 31, 2025 at 3:46 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> writes:
> > tzdata 2025b has been released on 3/22[1]. Do we need to update the
> > tzdata.zi file on HEAD and backbranches?
>
> Yup, eventually, but I don't normally worry about it until we are
> approaching a release date. tzdata changes often come in bunches
> around the spring and fall equinoxes, which is when governments
> tend to rush out DST changes without thinking about lead times :-(.
> So it's entirely possible that 2025b will already be obsolete by May.
> (See for example ecbac3e6e and d8fc45bd0, when I thought I'd waited
> long enough and was wrong.)
>
> The situation might be different with a tzdata release that affects
> our regression test results, but I don't believe this one does.
>
Thank you for the explanation! That makes sense. We'll revisit it
around minor release.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alena Rybakina | 2025-03-31 23:10:58 | Re: Replace IN VALUES with ANY in WHERE clauses during optimization |
Previous Message | Jacob Champion | 2025-03-31 23:09:22 | Re: pgsql: Add support for OAUTHBEARER SASL mechanism |