From 6a6f4cc5bc2910c9f22c268d1f10a7ac407f6e05 Mon Sep 17 00:00:00 2001 From: Andrey Borodin Date: Thu, 26 Mar 2026 22:55:55 +0500 Subject: [PATCH v2 2/2] Small improvements --- doc/src/sgml/func/func-binarystring.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/func/func-binarystring.sgml b/doc/src/sgml/func/func-binarystring.sgml index 9f731d7bca0..dc6b7e57ea7 100644 --- a/doc/src/sgml/func/func-binarystring.sgml +++ b/doc/src/sgml/func/func-binarystring.sgml @@ -778,14 +778,14 @@ RFC 4648 Section 7. It uses the extended hex alphabet (0-9 and - A-V) which preserves the lexicographical - sort order of the encoded data. The encode function + A-V) which preserves the sort order of + the encoded data when compared byte-wise. The encode function produces output padded with '=', while decode accepts both padded and unpadded input. Decoding is case-insensitive and ignores whitespace characters. - This format is useful for encoding UUIDs in a compact, sortable format: + This format is useful for encoding UUIDs in a compact, byte-wise sortable format: rtrim(encode(uuid_value::bytea, 'base32hex'), '=') produces a 26-character string compared to the standard 36-character UUID representation. -- 2.51.2