From: | Sergey Prokhorenko <sergeyprokhorenko(at)yahoo(dot)com(dot)au> |
---|---|
To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org>, Przemysław Sztoch <przemyslaw(at)sztoch(dot)pl>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Mat Arye <mat(at)timescaledb(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, Junwang Zhao <zhjwpku(at)gmail(dot)com> |
Subject: | Re: UUID v7 |
Date: | 2024-03-22 13:42:20 |
Message-ID: | 457249376.195310.1711114940632@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Why not use a single UUID generator for the database table in this case, similar to autoincrement?
Sergey Prokhorenko
sergeyprokhorenko(at)yahoo(dot)com(dot)au
On Friday, 22 March 2024 at 03:51:20 pm GMT+3, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
On 21.03.24 16:21, Jelte Fennema-Nio wrote:
> On Wed, 20 Mar 2024 at 19:08, Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>> Timer-based bits contribute to global sortability. But the real timers we have are not even millisecond adjusted. We can hope for ~few ms variation in one datacenter or in presence of atomic clocks.
>
> I think the main benefit of using microseconds would not be
> sortability between servers, but sortability between backends.
There is that, and there are also multiple backend workers for one session.
From | Date | Subject | |
---|---|---|---|
Next Message | Kartyshov Ivan | 2024-03-22 13:45:40 | Re: [HACKERS] make async slave to wait for lsn to be replayed |
Previous Message | Bruce Momjian | 2024-03-22 13:36:19 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |