pgsql: Improve worst-case performance of text_position_get_match_pos() - Mailing list pgsql-committers

From John Naylor
Subject pgsql: Improve worst-case performance of text_position_get_match_pos()
Date
Msg-id E1nG0xa-0005QF-E8@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Improve worst-case performance of text_position_get_match_pos()

This function converts a byte position to a character position after
a successful string match. Rather than calling pg_mblen() in a loop,
use pg_mbstrlen_with_len() since the latter can inline its own call to
pg_mblen(). When the string match is at the end of the haystack text, this
change results in 10-20% performance improvement, depending on platform and
typical character length in bytes. This also simplifies the code a little.

Specializing for UTF-8 could result in further improvement, but the
performance gain was not found to be reliable between platforms. The modest
gain in this commit is stable between platforms and usable by all server
encodings.

Discussion:
https://www.postgresql.org/message-id/CAFBsxsH1Yutrmu+6LLHKK8iXY+vG--Do6zN+2900spHXQNNQKQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b31e3f561365136b48d63e8561f32b697df16d1d

Modified Files
--------------
src/backend/utils/adt/varlena.c | 28 +++++-----------------------
1 file changed, 5 insertions(+), 23 deletions(-)


pgsql-committers by date:

Previous
From: Thomas Munro
Date:
Subject: pgsql: Track LLVM 14 API changes, up to 2022-01-30.
Next
From: Tom Lane
Date:
Subject: pgsql: First-draft release notes for 14.2.