RE: Use fadvise in wal replay - Mailing list pgsql-hackers

From Jakub Wartak
Subject RE: Use fadvise in wal replay
Date
Msg-id AM8PR07MB8248DAA91E79BE3B158A1ACFF6B39@AM8PR07MB8248.eurprd07.prod.outlook.com
Whole thread Raw
In response to Re: Use fadvise in wal replay  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: Use fadvise in wal replay
List pgsql-hackers
>> > On 21 Jun 2022, at 12:35, Amit Kapila <amit.kapila16@gmail.com> wrote:
>> >
>> > I wonder if the newly introduced "recovery_prefetch" [1] for PG-15 can
>> > help your case?
>>
>> AFAICS recovery_prefetch tries to prefetch main fork, but does not try to
>> prefetch WAL itself before reading it. Kirill is trying to solve the problem of
>> reading WAL segments that are our of OS page cache.

It seems that it is always by default set to 128 (kB) by default, another thing is that having (default) 16MB WAL
segmentsmight also hinder the readahead heuristics compared to having configured the bigger WAL segment size. 

Maybe the important question is why would be readahead mechanism be disabled in the first place via /sys | blockdev ?

-J.



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: Make COPY extendable in order to support Parquet and other formats
Next
From: Andrey Borodin
Date:
Subject: Re: Use fadvise in wal replay