Re: XLog size reductions: Reduced XLog record header size for PG17

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: XLog size reductions: Reduced XLog record header size for PG17
Date: 2024-04-07 05:37:25
Message-ID: C27A10AC-C97E-4786-8CDC-9754523D1C7D@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 3 Jan 2024, at 15:15, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> wrote:
>
> Hi and Happy New Year!
>
> I've looked through the patches and the change seems quite small and justified. But at the second round, some doubt arises on whether this long patchset indeed introduces enough performance gain? I may be wrong, but it saves only several bytes and the performance gain would be only in some specific artificial workload. Did you do some measurements? Do we have several percent performance-wise?
>
> Kind regards,
> Pavel Borisov

Hi Matthias!

This is a kind reminder that the thread is waiting for your reply. Are you interesting in CF entry [0]?

Thanks!

Best regards, Andrey Borodin.
[0] https://commitfest.postgresql.org/47/4386/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2024-04-07 07:30:06 Re: Improve heapgetpage() performance, overhead from serializable
Previous Message Andrey M. Borodin 2024-04-07 05:29:40 Re: Change prefetch and read strategies to use range in pg_prewarm ... and raise a question about posix_fadvise WILLNEED