diff options
author | John Naylor <john.naylor@postgresql.org> | 2024-01-16 16:32:48 +0700 |
---|---|---|
committer | John Naylor <john.naylor@postgresql.org> | 2024-01-19 12:56:15 +0700 |
commit | 0aba2554409ee3251d7558567edd114d8ed36dcc (patch) | |
tree | 286b5418f1988aee89bda055367f91234e164abd /src/backend/access/gist/gistutil.c | |
parent | e97b672c88f6e5938a2b81021bd4b590b013976f (diff) | |
download | postgresql-0aba2554409ee3251d7558567edd114d8ed36dcc.tar.gz postgresql-0aba2554409ee3251d7558567edd114d8ed36dcc.zip |
Add optimized C string hashing
Given an already-initialized hash state and a NUL-terminated string,
accumulate the hash of the string into the hash state and return the
length for the caller to (optionally) save for the finalizer. This
avoids a strlen call.
If the string pointer is aligned, we can use a word-at-a-time
algorithm for NUL lookahead. The aligned case is only used on 64-bit
platforms, since it's not worth the extra complexity for 32-bit.
Handling the tail of the string after finishing the word-wise loop
was inspired by NetBSD's strlen(), but no code was taken since that
is written in assembly language.
As demonstration, use this in the search path cache. This brings the
general case performance closer to the special case optimization done
in commit a86c61c9ee. There are other places that could benefit, but
that is left for future work.
Jeff Davis and John Naylor
Reviewed by Heikki Linnakangas, Jian He, Junwang Zhao
Discussion: https://postgr.es/m/3820f030fd008ff14134b3e9ce5cc6dd623ed479.camel%40j-davis.com
Discussion: https://postgr.es/m/b40292c99e623defe5eadedab1d438cf51a4107c.camel%40j-davis.com
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions