From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Sequence vs UUID |
Date: | 2023-02-07 16:07:47 |
Message-ID: | CAFCRh--mkvA6nfb2VE-Zy80nHgriyKV9nMbS2iSTjwzrHW5mHw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Feb 7, 2023 at 3:47 PM Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Mon, Feb 6, 2023 at 1:22 PM Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
>
>> On 2023-02-06 20:04:39 +0100, Julian Backes wrote:
>> But UUIDs are random and that plays havoc with locality.
>
>
> This is really key. [...] the databases I've seen that are written with
> the
>
UUID pattern appear to be written by developers oblivious to this fact.
>
Well, perhaps these developers are not dealing with temporally clustered
data, like commerce related DB,
and more scientific data? In any case, this developer will definitely
investigate ULIDs, vs UUIDs, vs Ints (sequences),
based on the info from this thread. I'm aware of fragmentation issues, and
cache hit/miss issues etc, in general;
but was probably not sufficiently making the mental connection with UUIDs
and PostgreSQL. So thanks everyone.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey Borodin | 2023-02-07 16:24:44 | Re: Too coarse predicate locks granularity for B+ tree indexes |
Previous Message | Adrian Klaver | 2023-02-07 15:06:13 | Re: ALTER COLUMN to change GENERATED ALWAYS AS expression? |