> On Aug 8, 2021, at 1:25 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > Ugh. The regex engine is finding the match correctly, but it's failing to > tell the caller where it is :-(. I was a little too cute in optimizing > the regmatch_t result-vector copying in pg_regexec, and forgot to ensure > that the overall match position would be reported. > > Thanks for the testing! Sure! Thanks for improving the regular expression engine! I have applied your latest patch and do not see any problems with it. All my tests pass with no asserts and with no differences in results vs. master. This is a test suite of nearly 1.5 million separate regular expressions. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
- Another regexp performance improvement: skip useless paren-... Tom Lane
- Re: Another regexp performance improvement: skip usele... Andrew Dunstan
- Re: Another regexp performance improvement: skip u... Tom Lane
- Re: Another regexp performance improvement: sk... Mark Dilger
- Re: Another regexp performance improvement... Tom Lane
- Re: Another regexp performance improv... Mark Dilger
- Re: Another regexp performance im... Tom Lane
- Re: Another regexp performanc... Mark Dilger
- Re: Another regexp performanc... Tom Lane
- Re: Another regexp performanc... Mark Dilger
- Re: Another regexp performanc... Tom Lane
- Re: Another regexp performanc... Mark Dilger
- Re: Another regexp performanc... Tom Lane
- Re: Another regexp performanc... Tom Lane
- Re: Another regexp performanc... Tom Lane
- Re: Another regexp performanc... Mark Dilger
- Re: Another regexp performanc... Mark Dilger
- Re: Another regexp performanc... Tom Lane