Re: Why don't you to document pg_shmem_allocations view's name list?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Why don't you to document pg_shmem_allocations view's name list?
Date: 2020-05-26 02:08:55
Message-ID: 20200526020855.GC6155@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 26, 2020 at 10:16:19AM +0900, Masahiro Ikeda wrote:
> I think it is more useful if the name list of the
> pg_shmem_allocations view is listed in one page.
>
> Why don't you document pg_shmem_allocations view's name list?

Documenting that would create a dependency between the docs and the
backend code, with very high chances of missing doc updates each time
new code that does an extra shared memory allocation is added. I
think that there would be a point in bringing more sanity and
consistency to the names of the shared memory sections passed down to
ShmemInitStruct() and SimpleLruInit() though.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2020-05-26 02:10:03 Re: pg_ls_tmpdir to show directories and shared filesets (and pg_ls_*)
Previous Message Craig Ringer 2020-05-26 02:06:53 Re: [PATCH] Fix install-tests target for vpath builds