Re: SIMILAR TO expressions translate wildcards where they shouldn't

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: SIMILAR TO expressions translate wildcards where they shouldn't
Date: 2025-05-27 10:24:33
Message-ID: 37584c1321b984a0c5c05d213ef70b869d95a12a.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 2025-05-27 at 14:57 +0900, Michael Paquier wrote:
> Anyway, that's really hard to parse so I would suggest to split each
> check into queries of their own to show individual conversions in
> these EXPLAIN outputs (we don't care if tese regexps are correct, just
> want to check the output to the POSIX style).  I am OK with the point
> based on charclass_start to count the number of carets at the
> beginning of a character class.
>
> With some tweaks and the tests reworked, I am finishing with the
> reviewed version attached.  What do you think?

Thank you; I think that is good to go.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-05-27 14:54:12 Re: SIMILAR TO expressions translate wildcards where they shouldn't
Previous Message PG Bug reporting form 2025-05-27 10:11:58 BUG #18937: New error class 10 for XQuery errors lacks a "standard" error code