Re: tzdata 2025b - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: tzdata 2025b
Date
Msg-id CAD21AoDr-nXm-7MtamG2fPYsS1ZkD4DvOBp2HNHLk5--7DDz6g@mail.gmail.com
Whole thread Raw
In response to Re: tzdata 2025b  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Mar 31, 2025 at 3:46 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Masahiko Sawada <sawada.mshk@gmail.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



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: pgsql: Add support for OAUTHBEARER SASL mechanism
Next
From: Alena Rybakina
Date:
Subject: Re: Replace IN VALUES with ANY in WHERE clauses during optimization