Re: pgsql: Update time zone data files to tzdata release 2024b.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Update time zone data files to tzdata release 2024b.
Date: 2024-10-30 20:14:37
Message-ID: CAD5tBcLHz6NLCW_65qYka08HRVeT6w15Cd1YFKmHV5Ou43Fu4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Oct 30, 2024 at 11:00 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > On Oct 29, 2024, at 5:41 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> I would expect that the upgrade tests would pass now for upgrades
> >> from v12 or later, thanks to b8ea0f675 et al, but I'm not real
> >> sure what to do about testing the out-of-support branches. Should
> >> we back-patch b8ea0f675 as far down as 9.2?
>
> > Or fix/remove the problem rows in AdjustUpgrade.pm I guess
>
> I went to try to test this locally, and got nowhere, because:
>
> old cluster does not use data checksums but the new one does
> Failure, exiting
>
> What have you done to get around that on crake?
>
>
>

I did this:

https://github.com/PGBuildFarm/client-code/commit/2ef5acefe5e6eee761ea2ee010c3d14e2d8fab60

I was intending to push a new client release with it but things got kinda
screwy the last 10 days. I will try to push it out later this week.

Meanwhile I think you should see the same result without this issue if you
test using v17 or earlier instead of master.

cheers

andrew

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2024-10-30 20:33:20 Re: pgsql: Update time zone data files to tzdata release 2024b.
Previous Message Peter Geoghegan 2024-10-30 19:53:41 pgsql: nbtree: assert no scheduled primscan between pages.