Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6FNe-00BfhH-M5 for pgsql-committers@arkaria.postgresql.org; Wed, 30 Oct 2024 20:33:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t6FNc-00CGwm-Uj for pgsql-committers@arkaria.postgresql.org; Wed, 30 Oct 2024 20:33:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6FNc-00CGwe-Nj for pgsql-committers@lists.postgresql.org; Wed, 30 Oct 2024 20:33:25 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6FNa-003fzg-E0 for pgsql-committers@lists.postgresql.org; Wed, 30 Oct 2024 20:33:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 49UKXKDk764323; Wed, 30 Oct 2024 16:33:20 -0400 From: Tom Lane To: Andrew Dunstan cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Update time zone data files to tzdata release 2024b. In-reply-to: References: <362289.1730241666@sss.pgh.pa.us> <55A5E01C-1B0F-40F9-94EA-FEDED1575C92@dunslane.net> <595311.1730300440@sss.pgh.pa.us> Comments: In-reply-to Andrew Dunstan message dated "Wed, 30 Oct 2024 16:14:37 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <764321.1730320400.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 30 Oct 2024 16:33:20 -0400 Message-ID: <764322.1730320400@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > On Wed, Oct 30, 2024 at 11:00=E2=80=AFAM Tom Lane wr= ote: >> 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/2ef5acefe5e6eee761ea2e= e010c3d14e2d8fab60 Ah, thanks. I installed that locally, and got ... tester:HEAD [16:25:31] saving files for cross-version upgrade che= ck tester:HEAD [16:25:33] checking upgrade from REL9_2_STABLE to HEA= D ... tester:HEAD [16:25:53] checking upgrade from REL_11_STABLE to HEA= D ... tester:HEAD [16:26:31] checking upgrade from REL_12_STABLE to HEA= D ... tester:HEAD [16:27:08] checking upgrade from REL_13_STABLE to HEA= D ... tester:HEAD [16:27:46] checking upgrade from REL_14_STABLE to HEA= D ... tester:HEAD [16:28:26] checking upgrade from REL_15_STABLE to HEA= D ... tester:HEAD [16:29:05] checking upgrade from REL_16_STABLE to HEA= D ... 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. regards, tom lane