Re: [PATCH] Add memory usage reporting to VACUUM VERBOSE

From: 河田達也 <kawatatatsuya0913(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Add memory usage reporting to VACUUM VERBOSE
Date: 2025-11-21 16:25:58
Message-ID: CAHza6qfQYS3EAc5OKc+Jwejdxzg+Fn3jhb9XDsH_Xf=UhAx=UA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Sawada-san,

Thank you for your additional feedback on v4!

>We can initialize dead_items_max_bytes when declared.
Thank you. I fixed it as you mentioned.

>Does it need to check if vacrel->dead_items is non-NULL?
Thank you. I fixed it as you mentioned.

>I think we should not use "index scans" since the number doesn't
>actually represent the number of index scans performed. How about
>something like:
>
>memory usage: 1.02 MB in total, with dead-item storage reset 15 times
>(limit was 0.06 MB)
>
>Also when it comes to the plural, we can use errmsg_plural() instead.
Thank you. I fixed the message as you mentioned.
Also, I found that ngettext() with appendStringInfo() is a standard pattern
in the PostgreSQL codebase (e.g., src/backend/catalog/pg_shdepend.c,
src/backend/catalog/dependency.c), so I use ngettext() in this code.

If it's good to use errmsg_plural(), I can restructure the code to use
errmsg_plural().

Best regards,
Tatsuya Kawata

Attachment Content-Type Size
v5-0001-Add-memory-usage-reporting-to-VACUUM-VERBOSE.patch application/x-patch 3.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-11-21 16:38:37 Re: RFC 9266: Channel Bindings for TLS 1.3 support
Previous Message Jacob Champion 2025-11-21 16:18:41 Re: RFC 9266: Channel Bindings for TLS 1.3 support