Re: Align memory context level numbering in pg_log_backend_memory_contexts()

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Align memory context level numbering in pg_log_backend_memory_contexts()
Date: 2025-04-18 08:54:04
Message-ID: 1ad6d388-1b43-400d-bec9-36d52f755f74@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025/04/18 6:11, David Rowley wrote:
> On Fri, 18 Apr 2025 at 00:25, Rahila Syed <rahilasyed90(at)gmail(dot)com> wrote:
>> Regarding v2 patch,
>> - int level = 0;
>>
>> Retaining the level variable will enhance the code readability, IMO.
>
> When I read that, I suspected it might have been leftover from a
> refactor during the development that was forgotten about. There'd be
> thousands of places in our code base that you could make the
> readability argument for, including the max_level and max_children
> parameters at the same call-site. But those didn't get the same
> treatment.
>
> I've now pushed the latest patch. Thanks for the reviews.

Shouldn't the example output of pg_log_backend_memory_contexts() in
the documentation also be updated to use 1-based numbering for consistency?
Patch attached.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment Content-Type Size
v1-0001-doc-Fix-memory-context-level-in-pg_log_backend_me.patch text/plain 2.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2025-04-18 09:17:21 Re: Changing shared_buffers without restart
Previous Message Frédéric Yhuel 2025-04-18 08:49:58 [BUG] temporary file usage report with extended protocol and unnamed portals