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

2020-05-25 Thread Masahiro Ikeda
Hello, I think it is more useful if the name list of the pg_shmem_allocations view is listed in one page. For example, * Wal Sender Ctl: walsender-related shared memory * AutoVacuum Data: autovacuum-related shared memory * PROCLOCK hash: shared memory for hash table for PROCLOCK structs Why don

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

2020-05-25 Thread Michael Paquier
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

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

2020-05-26 Thread Masahiro Ikeda
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 c