| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Tatsuya Kawata <kawatatatsuya0913(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-12-30 21:18:57 |
| Message-ID: | CAD21AoBDTwy9dSm+o8uOT2iWrSWaMELm8h-fohom1qmjaAZz3g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 29, 2025 at 7:24 PM Tatsuya Kawata
<kawatatatsuya0913(at)gmail(dot)com> wrote:
>
> Hi Sawada-san and Chao-san,
>
> Thank you both for your continued reviews and feedback on this patch.I agree with both points that could be misleading.
> I've updated the message as follows:
>
> memory usage: dead item storage %.2f MB accumulated across %d resets (limit %.2f MB each)
>
> This wording:
> - Use both "memory usage:" prefix and "dead item storage" to be consistent with other existing log lines (buffer usage:, WAL usage:, system usage:) and to clarify what kind of memory we're reporting
> - Clearly indicate that the value is a cumulative sum of snapshots, not actual memory allocation
> - Use "across %d resets" to show the relationship between the accumulated value and reset count
> - Keep "limit %.2f MB each" to indicate the per-reset memory limit
>
> Please find attached the v11 patch.
>
The patch looks good to me, so I've pushed the patch.
Kawata-san, my apologies, I missed to credit your name as the author.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-12-30 22:50:10 | Re: Can we remove support for standard_conforming_strings = off yet? |
| Previous Message | Alexander Pyhalov | 2025-12-30 19:04:21 | Re: Asynchronous MergeAppend |