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

From: Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-27 04:14:51
Message-ID: 07949e3c41a4098dec2341b689d8863e@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-05-26 11:08, Michael Paquier wrote:
> 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

Thanks for replaying.

I understood the reason why the name list is not documented.
I agree your opinion.

Regards,

--
Masahiro Ikeda

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-05-27 05:10:00 Re: Default gucs for EXPLAIN
Previous Message Isaac Morland 2020-05-27 02:56:39 Re: max_slot_wal_keep_size comment in postgresql.conf