Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions

Aleksander Alekseev <aleksander@tigerdata.com>

From: Aleksander Alekseev <aleksander@tigerdata.com>

To: pgsql-hackers <pgsql-hackers@postgresql.org>

Cc: Sergey Prokhorenko <sergeyprokhorenko@yahoo.com.au>

Date: 2025-10-23T15:08:29Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add base32hex support to encode() and decode() functions.
- 497c1170cb10 19 (unreleased) landed
Allow explicit casting between bytea and uuid.
- ba21f5bf8aff 19 (unreleased) landed
Add support for base64url encoding and decoding
- e1d917182c19 19 (unreleased) cited

Attachments

hi-hackers.txt (text/plain)

Hi,

> > I'm writing to propose adding two new built-in functions to PostgreSQL that provide compact UUID encoding using the base32hex format.
>
> Firstly, cc:'ing a few dozens of people is not the best way to get
> attention to your patch. Please don't do this.
>
> [...]

I checked pgsql-hackers@ archive [1] and if I understand correctly
Sergey is not on the mailing list. So people that were not cc:'ed
didn't receive his e-mail. I attached the original text for those
interested and also for history.

Sergey, please make sure you are subscribed to the mailing list [2].

[1]: https://www.postgresql.org/message-id/CAJ7c6TOramr1UTLcyB128LWMqita1Y7%3Darq3KHaU%3Dqikf5yKOQ%40mail.gmail.com
[2]: https://www.postgresql.org/list/

-- 
Best regards,
Aleksander Alekseev