aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorTomas Vondra <tomas.vondra@postgresql.org>2025-04-07 22:54:49 +0200
committerTomas Vondra <tomas.vondra@postgresql.org>2025-04-07 23:08:17 +0200
commit8cc139bec34a2971b0682a04eb52ce7b3f5bb425 (patch)
tree67e2f302199d1ac5fe406961ccd5fe47f469bdf9 /src/backend/tcop/postgres.c
parent65c298f61fc70f2f960437c05649f71b862e2c48 (diff)
downloadpostgresql-8cc139bec34a2971b0682a04eb52ce7b3f5bb425.tar.gz
postgresql-8cc139bec34a2971b0682a04eb52ce7b3f5bb425.zip
Introduce pg_shmem_allocations_numa view
Introduce new pg_shmem_alloctions_numa view with information about how shared memory is distributed across NUMA nodes. For each shared memory segment, the view returns one row for each NUMA node backing it, with the total amount of memory allocated from that node. The view may be relatively expensive, especially when executed for the first time in a backend, as it has to touch all memory pages to get reliable information about the NUMA node. This may also force allocation of the shared memory. Unlike pg_shmem_allocations, the view does not show anonymous shared memory allocations. It also does not show memory allocated using the dynamic shared memory infrastructure. Author: Jakub Wartak <jakub.wartak@enterprisedb.com> Reviewed-by: Andres Freund <andres@anarazel.de> Reviewed-by: Bertrand Drouvot <bertranddrouvot.pg@gmail.com> Reviewed-by: Tomas Vondra <tomas@vondra.me> Discussion: https://postgr.es/m/CAKZiRmxh6KWo0aqRqvmcoaX2jUxZYb4kGp3N%3Dq1w%2BDiH-696Xw%40mail.gmail.com
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions