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

Поиск
Список
Период
Сортировка
От Andrey M. Borodin
Тема Re: Change prefetch and read strategies to use range in pg_prewarm ... and raise a question about posix_fadvise WILLNEED
Дата
Msg-id 6F932536-AE43-4EEB-A1DE-38FDD4826F6D@yandex-team.ru
обсуждение исходный текст
Ответ на Re: Change prefetch and read strategies to use range in pg_prewarm ... and raise a question about posix_fadvise WILLNEED  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Ответы Re: Change prefetch and read strategies to use range in pg_prewarm ... and raise a question about posix_fadvise WILLNEED  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 

> On 15 Mar 2024, at 17:12, Nazir Bilal Yavuz <byavuz81@gmail.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/

В списке pgsql-hackers по дате отправления:

Предыдущее
От: John Naylor
Дата:
Сообщение: Re: Improve heapgetpage() performance, overhead from serializable
Следующее
От: "Andrey M. Borodin"
Дата:
Сообщение: Re: XLog size reductions: Reduced XLog record header size for PG17