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

From: Илья Чердаков <i(dot)cherdakov(dot)pg(at)gmail(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Sergey Prokhorenko <sergeyprokhorenko(at)yahoo(dot)com(dot)au>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions
Date: 2025-11-20 05:46:43
Message-ID: aa24964a-f0d7-435e-9254-bb69823948d6@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

31.10.2025 2:10, Masahiko Sawada wrote:
> ---
> I think we should update the documentation in the uuid section about
> casting data between bytea and uuid. For references, we have a similar
> description for bytea and integer[1].
Greetings!
I briefly tested the patched version of v3. The implemented
functionality works correctly.

---
You can also add a case with the error from v3-0002
"invalid base32hex end sequence" to the tests :

+        ereport(ERROR,
+                (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
+                 errmsg("invalid base32hex end sequence"),
+                 errhint("Input data has non-zero padding bits.")));

---
I agree with Masahiko Sawada; information about conversions
should be added to the documentation.

--
Best regards,
Ilya Cherdakov, PostgresPro

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-11-20 05:51:56 Re: gen_guc_tables.pl: Validate required GUC fields before code generation
Previous Message Chao Li 2025-11-20 04:22:54 Re: [PATCH] Add memory usage reporting to VACUUM VERBOSE