From: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, dgrowleyml(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-16 14:19:59 |
Message-ID: | f56063dfad48f5121e5ab733b36ec46d@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-04-16 06:18, Daniel Gustafsson wrote:
>> On 15 Apr 2025, at 23:03, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
>> My vote is to make the levels 1-based in all locations where we output
>> the context information.
>
> I agree with this, pg_get_process_memory_contexts() also use 1-based
> levels
> fwiw.
+1.
I believe there's no particular issue with starting the level from 1 in
pg_log_backend_memory_contexts().
Regarding the implementation:
In the initial patch attached, I naïvely incremented the level just
before emitting the log line.
However, it might be cleaner to simply initialize the level variable to
1 from the start. This could help avoid unnecessary confusion when
debugging that part of the code.
Similarly, I noticed that in pg_get_process_memory_contexts(), the level
is initialized to 0 in ProcessGetMemoryContextInterrupt(void):
int level = 0;
..
MemoryContextStatsInternal(c, level, 100, 100, &grand_totals, ..
If we want to be consistent, perhaps it would make sense to start from 1
there as well.
BTW level variable has existed since before pg_backend_memory_contexts
was introduced — it was originally used for functions that help inspect
memory contexts via the debugger. Because of that, I think changing this
would affect not only these functions codes but some older ones.
--
Atsushi Torikoshi
Seconded from NTT DATA GROUP CORPORATION to SRA OSS K.K.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2025-04-16 14:20:34 | Re: Typos in the comment for the estimate_multivariate_ndistinct() |
Previous Message | Daniel Gustafsson | 2025-04-16 14:19:02 | Re: pg_dump: Fix dangling pointer in EndCompressorZstd() |