From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
Date: Mon, 11 Mar 2024 14:17:04 -0700
Message-ID: <b7aa2315917b4090a611ca07c7713c348f9df98d.camel@j-davis.com> (raw)
In-Reply-To: <1548559.1710188512@sss.pgh.pa.us>
References: <E1rj5WA-002z5V-WA@gemulon.postgresql.org>
<8899c7c62b86370076110920686fd24863b69a01.camel@j-davis.com>
<1222780.1710047108@sss.pgh.pa.us>
<0ef325fa06e7a1605c4e119c4ecb637c67e5fb4e.camel@j-davis.com>
<1547879.1710188139@sss.pgh.pa.us>
<1548559.1710188512@sss.pgh.pa.us>
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
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: pgsql@j-davis.com, tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
In-Reply-To: <b7aa2315917b4090a611ca07c7713c348f9df98d.camel@j-davis.com>
* 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