Re: Change prefetch and read strategies to use range in pg_prewarm ... and raise a question about posix_fadvise WILLNEED

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Cédric Villemain <Cedric(dot)Villemain(at)abcsql(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change prefetch and read strategies to use range in pg_prewarm ... and raise a question about posix_fadvise WILLNEED
Date: 2024-04-07 05:29:40
Message-ID: 6F932536-AE43-4EEB-A1DE-38FDD4826F6D@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 15 Mar 2024, at 17:12, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
>
> I did not have the time to check other things you mentioned but I
> tested the read performance. The table size is 5.5GB, I did 20 runs in
> total.

Hi Nazir!

Do you plan to review anything else? Or do you think it worth to look at by someone else? Or is the patch Ready for Committer? If so, please swap CF entry [0] to status accordingly, currently it's "Waiting on Author".

Best regards, Andrey Borodin.

[0] https://commitfest.postgresql.org/47/4763/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey M. Borodin 2024-04-07 05:37:25 Re: XLog size reductions: Reduced XLog record header size for PG17
Previous Message John Naylor 2024-04-07 05:07:22 Re: Improve heapgetpage() performance, overhead from serializable