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

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>
Cc: Sergey Prokhorenko <sergeyprokhorenko(at)yahoo(dot)com(dot)au>, 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 12:24:49
Message-ID: CAGECzQS4s0GRsNqyCdnOmx3rUUdboQumFV0V2GACqBoBRDpQ2w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 28 Oct 2025 at 12:53, Dagfinn Ilmari Mannsåker
<ilmari(at)ilmari(dot)org> wrote:
> If it's just one new form, do we need a separate decode function? Could
> we not just make uuid_in() accept both forms (they're easily
> distinguishable by length), like bytea_in accepts both the old escape
> format and the new hex format?
>
> And if the new format becomes the standard and want to change the
> default output format, we would need a GUC like bytea_output anyway, to
> let users control when to make the change.

Agreed to both of those. This seems too far out to spend much time
discussing now.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-10-28 12:25:01 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Previous Message jian he 2025-10-28 12:12:30 COPY FROM with RLS