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

From Alena Rybakina
Subject Re: Fix parallel vacuum buffer usage reporting
Date
Msg-id 611de844-d3f6-4395-9042-5c76203b7250@yandex.ru
Whole thread Raw
In response to Re: Fix parallel vacuum buffer usage reporting  (Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>)
Responses Re: Fix parallel vacuum buffer usage reporting
List pgsql-hackers

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

On 28.03.2024 13:12, Anthonin Bonnefoy wrote:
Hi, 

Thanks for the review.
 
On Thu, Mar 28, 2024 at 4:07 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
As for the proposed patch, the following part should handle the temp tables too:

True, I've missed the local blocks. I've updated the patch:
- read_rate and write_rate now include local block usage
- I've added a specific output for reporting local blocks instead of combining them in the same output.

Regards,
Anthonin
-- 
Regards,
Alena Rybakina
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Performance of JSON_TABLE vs jsonb_to_recordset
Next
From: "Anton A. Melnikov"
Date:
Subject: Re: Use XLOG_CONTROL_FILE macro everywhere?