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

On Wed, Oct 30, 2024 at 4:33 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

Andrew Dunstan <andrew@dunslane.net> writes:
> On Wed, Oct 30, 2024 at 11:00 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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

Ah, thanks.  I installed that locally, and got

...
tester:HEAD          [16:25:31] saving files for cross-version upgrade check
tester:HEAD          [16:25:33] checking upgrade from REL9_2_STABLE to HEAD ...
tester:HEAD          [16:25:53] checking upgrade from REL_11_STABLE to HEAD ...
tester:HEAD          [16:26:31] checking upgrade from REL_12_STABLE to HEAD ...
tester:HEAD          [16:27:08] checking upgrade from REL_13_STABLE to HEAD ...
tester:HEAD          [16:27:46] checking upgrade from REL_14_STABLE to HEAD ...
tester:HEAD          [16:28:26] checking upgrade from REL_15_STABLE to HEAD ...
tester:HEAD          [16:29:05] checking upgrade from REL_16_STABLE to HEAD ...
tester:HEAD          [16:29:47] checking upgrade from HEAD to HEAD ...
tester:HEAD          [16:30:32] running make ecpg check ...
tester:HEAD          [16:30:40] OK

(This client instance doesn't have back-branch runs for v9.3--v10.)

So now I'm even more confused.  Why does it work here and not there?
I can't think of any buildfarm options that would affect this.

My 9.2 saved instance is quite old ... Nov 2018.

But I don't see why that should affect it, so I'm confused too.