Re: Align memory context level numbering in pg_log_backend_memory_contexts()

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: 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-17 21:11:38
Message-ID: CAApHDvp49iH3smyoYTWynV7R4z1e=O9C16z7kW1Zs9uAQ7vGPw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2025-04-17 21:16:23 Re: Changing shared_buffers without restart
Previous Message Tom Lane 2025-04-17 19:59:28 SQL functions: avoid making a tuplestore unnecessarily