| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Sergey Prokhorenko <sergeyprokhorenko(at)yahoo(dot)com(dot)au> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions |
| Date: | 2025-10-28 14:39:26 |
| Message-ID: | CAGECzQT_gVVQeXhP23we75norKG64k4XQMAYP6s1B0G--D5uxw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 28 Oct 2025 at 15:29, Sergey Prokhorenko
<sergeyprokhorenko(at)yahoo(dot)com(dot)au> wrote:
> I believe we should put the discussion about compact UUID text encoding in PostgreSQL on hold for now.
I agree with respect to the dedicated encode_uuid and decode_uuid functions.
But I think having postgres support base32hex in encode/decode for
bytea seems like a sensible thing in any case. As well as conversion
between UUID and bytea. If someone wants to create patches for that,
it seems like there'd be enough support for those to get them merged.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryan Green | 2025-10-28 14:42:11 | [Patch] Windows relation extension failure at 2GB and 4GB |
| Previous Message | Daniil Davydov | 2025-10-28 14:32:19 | Re: Batching in executor |