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

From: Sergey Prokhorenko <sergeyprokhorenko(at)yahoo(dot)com(dot)au>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions
Date: 2025-10-25 19:15:48
Message-ID: 1522684793.499678.1761419748726@mail.yahoo.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 25 Oct 2025, at 04:31, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:>
> Or providing
> 'uuid_encode(uuid, format text) -> text' and 'uuid_decode(text, format
> text) -> uuid' might make sense too, but I'm not sure.
> On Saturday 25 October 2025 at 09:07:39 pm GMT+3, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> I like the idea, so I drafted a prototype for discussion.
> Though I do not see what else methods should be provided along with added one...

> Best regards, Andrey Borodin.

If base32hex becomes the default string representation for UUIDs in PostgreSQL, then the canonical UUID string representation may be added into these functions for backward compatibility.
Best regards,
Sergey Prokhorenko

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2025-10-26 01:25:48 Re: another autovacuum scheduling thread
Previous Message Jim Jones 2025-10-25 18:48:34 Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement