]> git.ipfire.org Git - thirdparty/postgresql.git/commit
doc: Clarify collation requirements for base32hex sortability.
authorMasahiko Sawada <msawada@postgresql.org>
Fri, 27 Mar 2026 19:13:29 +0000 (12:13 -0700)
committerMasahiko Sawada <msawada@postgresql.org>
Fri, 27 Mar 2026 19:13:29 +0000 (12:13 -0700)
commite752a2ccc98f324e7013cc4eabc1998d5a1020d0
treea8f5da3b18a75729cede3884743fc437e79919f2
parentd7965d65fc5bb2139bc51c051c11428414c65160
doc: Clarify collation requirements for base32hex sortability.

While fixing the base32hex UUID sortability test in commit
89210037a0a, it turned out that the expected lexicographical order is
only maintained under the C collation (or an equivalent byte-wise
collation). Natural language collations may employ different rules,
breaking the sortability.

This commit updates the documentation to explicitly state that
base32hex is "byte-wise sortable", ensuring users do not fall into the
trap of using natural language collations when querying their encoded
data.

Co-Authored-by: Andrey Borodin <x4mmm@yandex-team.ru>
Discussion: https://postgr.es/m/CAD21AoAwX1D6baSGuQXm0mzPXPWB07kgaoaaahjNHHenbdY24A@mail.gmail.com
doc/src/sgml/func/func-binarystring.sgml