Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions
Date
Msg-id 748CC2A1-FADF-4036-8E3E-2B2E678DCAB5@yandex-team.ru
Whole thread Raw
In response to Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

> On 26 Mar 2026, at 04:40, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I wonder whether this discovery puts enough of a hole in the
> value-proposition for base32hex that we should just revert
> this patch altogether.

After thinking more about it, I do not see grounds for reverting.

> "It works except in some locales"

It works per RFC. It adds value. It's documented precisely.

Sortability in cs_CZ only stands in a way for this format to become "the one UUID format to rule them all" instead of
canonicalin the future. 
We should let IETF WG know that digits and letters are not always ordered as they expect. Hopefully Sergey will handle
this.

BTW, thanks to Alexander and Masahiko for pushing this to finish line! I'm listed as author, but they done 99.9% of
workon making this functionality. 


Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Lukas Fittl
Date:
Subject: Re: Refactor query normalization into core query jumbling
Next
From: Nathan Bossart
Date:
Subject: Re: another autovacuum scheduling thread