From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
---|---|
To: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch> |
Cc: | postgre <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: UUID type question |
Date: | 2022-02-18 14:27:40 |
Message-ID: | CAFCRh-98cPFkCb3cfKDZyyU171vP8dha6TU6jSmoS1Au6gmCkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Feb 18, 2022 at 3:24 PM Dominique Devienne <ddevienne(at)gmail(dot)com> wrote:
> On Fri, Feb 18, 2022 at 3:06 PM Laura Smith
> <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch> wrote:
> > Is there anything inherently "special" about the UUID type ? i.e. if I store a UUID in a text is it "worse" ?
>
> uuid is stored as 16 binary bytes.
> Store it as text, and that's 36 chars (assuming UTF-8, double-that in
> UTF-16, if that's possible in PG).
> Or encode it as base-62 instead of hexa (base-16, with dashes), to use
> only 22 chars as text (in UTF-8 or ASCII)
You might also be interested in KSUID, e.g. https://github.com/segmentio/ksuid
From | Date | Subject | |
---|---|---|---|
Next Message | Laura Smith | 2022-02-18 14:54:30 | Re: UUID type question |
Previous Message | Marco DE BOOIJ | 2022-02-18 14:27:34 | Re: pg_upgrade from Postgresql-12 to Postgresql-13 fails with "Creating dump of database schemas postgres *failure*" |