Re: Fix parallel vacuum buffer usage reporting - Mailing list pgsql-hackers

From Anthonin Bonnefoy
Subject Re: Fix parallel vacuum buffer usage reporting
Date
Msg-id CAO6_XqrJeHrPtE9z0dt3O9xqq3097-LWO9xNYbnjh_iMmurzgw@mail.gmail.com
Whole thread Raw
In response to Re: Fix parallel vacuum buffer usage reporting  (Alena Rybakina <lena.ribackina@yandex.ru>)
Responses Re: Fix parallel vacuum buffer usage reporting
List pgsql-hackers
On Sat, Apr 20, 2024 at 2:00 PM Alena Rybakina <lena.ribackina@yandex.ru> wrote:

Hi, thank you for your work with this subject.

While I was reviewing your code, I noticed that your patch conflicts with another patch [0] that been committed.

[0] https://www.postgresql.org/message-id/flat/CA%2BhUKGJkOiOCa%2Bmag4BF%2BzHo7qo%3Do9CFheB8%3Dg6uT5TUm2gkvA%40mail.gmail.com


I've rebased the patch and also split the changes:
1: Use pgBufferUsage in Vacuum and Analyze block reporting
2: Stop tracking buffer usage in the now unused Vacuum{Hit,Miss,Dirty} variables
3: Remove declarations of Vacuum{Hit,Miss,Dirty}
Attachment

pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan
Next
From: jian he
Date:
Subject: slightly misleading Error message in guc.c