From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Some regular-expression performance hacking |
Date: | 2021-02-18 20:44:07 |
Message-ID: | ef5463ba-3e3c-45ec-bf02-27f91c6e09ab@www.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 18, 2021, at 20:58, Joel Jacobson wrote:
>Like you said earlier, perhaps the regex engine has been optimized enough for this time.
>If not, you want to investigate an additional idea,
In the above sentence, I meant "you _may_ want to".
I'm not at all sure these idea are applicable in the PostgreSQL regex engine,
so feel free to silently ignore these if you feel there is a risk for time waste.
>that I think can be seen as a generalization of the optimization trick for (.*),
>if I've understood how it works correctly.
Actually not sure if it can be seen as a generalization,
I just came to think of my ideas since they also improve
the case when you have lots of (.*) or bracket expressions of large ranges.
/Joel
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-02-18 20:44:47 | Re: Some regular-expression performance hacking |
Previous Message | Jacob Champion | 2021-02-18 20:33:18 | Re: Support for NSS as a libpq TLS backend |