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 1rjBN6-003zYV-L0 for pgsql-committers@arkaria.postgresql.org; Sun, 10 Mar 2024 05:05:17 +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 1rjBN4-0035IC-7C for pgsql-committers@arkaria.postgresql.org; Sun, 10 Mar 2024 05:05:14 +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 1rjBN3-0035I4-SM for pgsql-committers@lists.postgresql.org; Sun, 10 Mar 2024 05:05:14 +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 1rjBMz-003ju7-EU; Sun, 10 Mar 2024 05:05:12 +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 42A558Ek1222781; Sun, 10 Mar 2024 00:05:08 -0500 From: Tom Lane To: Jeff Davis cc: Jeff Davis , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Catalog changes preparing for builtin collation provider. In-reply-to: <8899c7c62b86370076110920686fd24863b69a01.camel@j-davis.com> References: <8899c7c62b86370076110920686fd24863b69a01.camel@j-davis.com> Comments: In-reply-to Jeff Davis message dated "Sat, 09 Mar 2024 19:53:41 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1222779.1710047108.1@sss.pgh.pa.us> Date: Sun, 10 Mar 2024 00:05:08 -0500 Message-ID: <1222780.1710047108@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jeff Davis writes: > On Sat, 2024-03-09 at 22:50 +0000, Jeff Davis wrote: >> Catalog changes preparing for builtin collation provider. > This is causing problems on a couple buildfarm members (mantid, > lapwing, snakefly) that all look like this: > ... > That's a little confusing to me: the '(?^:)' is just qr//, which should > match anything, right? Yeah. It looks to me like it's somehow Perl-version-related. The oldest Perl versions in the buildfarm (as of last month, last time I scraped these results) are longfin | 2024-02-08 11:16:05 | configure: using perl 5.14.0 lapwing | 2024-02-08 12:40:20 | configure: using perl 5.14.2 arowana | 2024-02-08 04:08:57 | configure: using perl 5.16.3 boa | 2024-02-07 16:10:12 | configure: using perl 5.16.3 buri | 2024-02-07 20:08:23 | configure: using perl 5.16.3 clam | 2024-02-08 15:00:10 | configure: using perl 5.16.3 dhole | 2024-02-08 06:09:13 | configure: using perl 5.16.3 mantid | 2024-02-08 14:07:10 | configure: using perl 5.16.3 parula | 2024-02-08 11:15:02 | configure: using perl 5.16.3 rhinoceros | 2024-02-08 11:52:11 | configure: using perl 5.16.3 siskin | 2024-02-07 20:16:39 | configure: using perl 5.16.3 snakefly | 2024-02-08 11:15:03 | configure: using perl 5.16.3 Of these, lapwing, mantid, and snakefly have failed; arowana succeeded, but it didn't run the pg_upgrade test; longfin succeeded, which I'm confused about; and the rest did not run yet. Not sure what to make of that, but I counsel sleeping on it and seeing what the remaining animals say. regards, tom lane