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

From Tom Lane
Subject Re: pgsql: Catalog changes preparing for builtin collation provider.
Date
Msg-id 1548559.1710188512@sss.pgh.pa.us
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
I wrote:
> Jeff Davis <pgsql@j-davis.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



pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Catalog changes preparing for builtin collation provider.
Next
From: Nathan Bossart
Date:
Subject: pgsql: reindexdb: Allow specifying objects to process in all databases.