On Fri, Nov 29, 2024 at 5:59 AM Sergey Prokhorenko <sergeyprokhore...@yahoo.com.au> wrote: > > > > Sergey Prokhorenko sergeyprokhore...@yahoo.com.au > > > On Friday 29 November 2024 at 09:19:33 am GMT+3, Masahiko Sawada > <sawada.m...@gmail.com> wrote: > > > On Thu, Nov 28, 2024 at 8:13 PM Sergey Prokhorenko > > <sergeyprokhore...@yahoo.com.au> wrote: > > > > I mean to add not benchmark results to the patch, but functions so that > > everyone can compare themselves on their equipment. The comparison with > > UUIDv4 is not very interesting, as the choice is usually between UUIDv7 and > > an integer key. And I have described many use cases, and in your benchmark > > there is only one, the simplest. > > > I don't think we should add such benchmark functions at least to this > patch. If there already is a well-established workload using UUIDv7 > and UUIDv4 etc, users can use pgbench with custom scripts, or it might > make sense to add it to pgbench as a built-in workload. Which however > should be a separate patch. Having said that, I think users should use > benchmarks that fit their workloads, and it would not be easy to > establish workloads that are reasonable for most systems. > > Regards, > > -- > Masahiko Sawada > Amazon Web Services: https://aws.amazon.com > > > > > > > Workloads can and must be added with parameters. Typically, companies use > test tables of 10,000 and 1,000,000 records, etc. Different companies have > mostly similar usage scenarios (for example, incremental loading). Each > company has to duplicate the work of others, creating the same benchmarks. > The worst thing is that this is entrusted to incompetent employees who are > not very good at understanding typical key usage scenarios. As a rule, these > are programmers, not system analysts. Accordingly, the solution in 99% of > cases will be in favor of integer keys, as they take up less space and are > generated faster. If we leave this problem until the next patch, it will take > us a year and a half. This is completely wrong.
There are still 4 months left until the feature freeze. We can discuss this topic and might find solutions. I don't think it's a blocker of this patch (UUIDv7 implementation patch). Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
