From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | benoit(dot)lobreau(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_shmem_allocations & documentation |
Date: | 2020-12-11 05:42:45 |
Message-ID: | X9MG1XrZBrTmLMWq@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 11, 2020 at 11:00:58AM +0900, Kyotaro Horiguchi wrote:
> Although we could just rip some words off, I'd like to propose instead
> to add an explanation why it is not exposed for anonymous allocations,
> like the column allocated_size.
Indeed, there is a hiccup between what the code does and what the docs
tell: the offset is not NULL for unused memory.
> - The offset at which the allocation starts. NULL for anonymous
> - allocations and unused memory.
> + The offset at which the allocation starts. For anonymous allocations,
> + no information about individual allocations is available, so the column
> + will be NULL in that case.
I'd say: let's be simple and just remove "and unused memory" because
anonymous allocations are... Anonymous so you cannot know details
related to them. That's something easy to reason about, and the docs
were written originally to remain simple.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Hou, Zhijie | 2020-12-11 06:43:56 | RE: Fail Fast In CTAS/CMV If Relation Already Exists To Avoid Unnecessary Rewrite, Planning Costs |
Previous Message | Michael Paquier | 2020-12-11 05:21:57 | Re: pg_waldump error message fix |