Re: Support regular expressions with nondeterministic collations - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Support regular expressions with nondeterministic collations
Date
Msg-id aba93eda-6215-4bff-bab7-6e0656a028e9@eisentraut.org
Whole thread Raw
In response to Re: Support regular expressions with nondeterministic collations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Support regular expressions with nondeterministic collations
List pgsql-hackers
On 22.10.24 16:40, Tom Lane wrote:
> Peter Eisentraut <peter@eisentraut.org> writes:
>> This patch allows using regular expression functions and operators with
>> nondeterministic collations.
>> ...
>> In summary, this patch doesn't change any functionality that currently
>> works.  It just removes one error message and lets regular expressions
>> just run, independent of whether the collation is nondeterministic.
> 
> I kind of wonder if we really want to do this.  It adds no
> functionality, and it forecloses the possibility of changing
> the definition later.  I understand and agree with your conclusion
> that it's pretty much impossible to do what the SQL standard suggests
> should happen --- but maybe we're both missing something that would
> make it feasible.  (Have you asked your committee colleagues if
> anyone's actually implemented what they wrote about SIMILAR TO?
> If they've written something unimplementable, it seems like there
> is work for them to do in any case.)

Good idea; I'll go ask there too.

Btw., one end goal here is to be able to run with a nondeterministic 
collation as the global locale.  So for example you could make the whole 
system insensitive to Unicode normalization forms.  But if that 
effectively globally disables regular expressions, then people will be 
sad, and also most of psql breaks, and so on.  So some positive solution 
here would be useful.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: -Wformat-signedness
Next
From: Yushi Ogiwara
Date:
Subject: Re: Fix for consume_xids advancing XIDs incorrectly