From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Jeff Davis <jdavis@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
Date: Sun, 10 Mar 2024 00:05:08 -0500
Message-ID: <1222780.1710047108@sss.pgh.pa.us> (raw)
In-Reply-To: <8899c7c62b86370076110920686fd24863b69a01.camel@j-davis.com>
References: <E1rj5WA-002z5V-WA@gemulon.postgresql.org>
<8899c7c62b86370076110920686fd24863b69a01.camel@j-davis.com>
Jeff Davis <pgsql@j-davis.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql@j-davis.com, jdavis@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
In-Reply-To: <1222780.1710047108@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox