Re: pgsql: Catalog changes preparing for builtin collation provider. - Mailing list pgsql-committers

From Jeff Davis
Subject Re: pgsql: Catalog changes preparing for builtin collation provider.
Date
Msg-id b7aa2315917b4090a611ca07c7713c348f9df98d.camel@j-davis.com
Whole thread Raw
In response to Re: pgsql: Catalog changes preparing for builtin collation provider.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Catalog changes preparing for builtin collation provider.
List pgsql-committers
On Mon, 2024-03-11 at 16:21 -0400, Tom Lane wrote:
> Oh!  No, it's a "feature": man perlop quoth

Wow.

> So we actually need to find and nuke all of these, not just the one
> that's causing trouble.

For now I committed the one change to fix the buildfarm.

I am still confused on a couple of points here, such as: why does my
example work fine on newer versions of perl?

But I agree: if the empty pattern is magical, we should get rid of it,
even if we don't understand the exact conditions under which it behaves
magically.

Reagrds,
    Jeff Davis




pgsql-committers by date:

Previous
From: Jeff Davis
Date:
Subject: pgsql: Fix 002_pg_upgrade.pl.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.