Re: pgsql: Catalog changes preparing for builtin collation provider.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
Date: 2024-03-11 20:21:52
Message-ID: 1548559.1710188512@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

I wrote:
> Jeff Davis <pgsql(at)j-davis(dot)com> writes:
>> That's so bizarre that I have to guess that it's a perl bug.

> I agree.

Oh! No, it's a "feature": man perlop quoth

The empty pattern "//"
If the PATTERN evaluates to the empty string, the last
successfully matched regular expression is used instead. In
this case, only the "g" and "c" flags on the empty pattern are
honored; the other flags are taken from the original pattern.
If no match has previously succeeded, this will (silently) act
instead as a genuine empty pattern (which will always match).

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

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2024-03-11 20:43:12 pgsql: reindexdb: Allow specifying objects to process in all databases.
Previous Message Tom Lane 2024-03-11 20:15:39 Re: pgsql: Catalog changes preparing for builtin collation provider.