MIME-Version: 1.0
References: <1791665551.452444.1761209220211.ref@mail.yahoo.com>
 <1791665551.452444.1761209220211@mail.yahoo.com>
 <CAJ7c6TOramr1UTLcyB128LWMqita1Y7=arq3KHaU=qikf5yKOQ@mail.gmail.com>
 <18022523-0F8F-4C07-AFF5-57DC9086D78E@yandex-team.ru>
 <1895971769.8343.1761240853939@mail.yahoo.com>
 <CAD21AoCxy_3VW2_z5Rxc-tFsuqeyGsA-F_kD-tx6XXBC56nTCg@mail.gmail.com>
 <574624399.175025.1761290201491@mail.yahoo.com>
 <CAD21AoAXQcZ2mMkxX6NPdFpdC-D3AhE--qyH9Se3XTrDX6x-bg@mail.gmail.com>
 <953203149.383019.1761345585325@mail.yahoo.com>
 <CAD21AoCzEDdwpyPwA0d-QmCRe5rMz3m160SJgxMwKke85e8n0w@mail.gmail.com>
 <6F76FA61-E2DC-44EF-9504-889D9BDB4EBD@yandex-team.ru>
In-Reply-To: <6F76FA61-E2DC-44EF-9504-889D9BDB4EBD@yandex-team.ru>
From: Aleksander Alekseev <aleksander@tigerdata.com>
Date: Mon, 27 Oct 2025 13:23:27 +0300
Message-ID: 
 <CAJ7c6TOqZxNoXVEY31BZqfAxKoE37Y4Ruq_+830z_yYRJiCahA@mail.gmail.com>
Subject: Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in
 functions
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>,
 Masahiko Sawada <sawada.mshk@gmail.com>,
	Sergey Prokhorenko <sergeyprokhorenko@yahoo.com.au>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAJ7c6TOqZxNoXVEY31BZqfAxKoE37Y4Ruq_%2B830z_yYRJiCahA%40mail.gmail.com>
Precedence: bulk

Hi,

> > Or providing
> > 'uuid_encode(uuid, format text) -> text' and 'uuid_decode(text, format
> > text) -> uuid' might make sense too, but I'm not sure.
>
> 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...

I see no reason why we should forbid the use of base32 encoding with
bytea. Or have different functions for this e.g. uuid_encode() and
encode(). To me it looks like a poor API design.

-- 
Best regards,
Aleksander Alekseev