Skip to content
← Catalog atlas / pg_shmem_allocations_numa

SYSTEM VIEW · System view

pg_shmem_allocations_numa

The pg_shmem_allocations_numa shows how shared memory allocations in the server's main shared memory segment are distributed across NUMA nodes. This includes both memory allocated by PostgreSQL itself and memory allocated by extensions using the mechanisms detailed in Section 36.10.11. This view will output multiple rows for each of the shared memory segments provided that they are spread across multiple NUMA nodes. This view should not be queried by monitoring systems as it is very slow and may end up allocating shared memory in case it was not used earlier. Current limitation for this view is that won't show anonymous shared memory allocations. Note that this view does not include memory allocated using the dynamic shared memory infrastructure.

First seen PG 18Last seen PG 19Columns 3

Checked column by column against a PostgreSQL 18.6 instance · Raw measurement record ↗

Columns PostgreSQL 18

pg_shmem_allocations_numa
COLUMNTYPEDESCRIPTION
name text The name of the shared memory allocation.
numa_node integerDocumented as:int4 ID of NUMA node
size bigintDocumented as:int8 Size of the allocation on this particular NUMA memory node in bytes

Columns marked "implicit" are not included in SELECT *; some early statistics views are completed from same-version source, and the extra provenance is shown in the column description.

Column evolution matrix

Hover a cell for the column type
PresentAdded / type or attribute changeRemoved
COLUMN9.09.19.29.39.49.59.610111213141516171819
name
numa_node
size

9.0 is the coverage baseline; a column already present in the baseline is not marked as added. The matrix aligns columns by name, so a rename appears as the old column removed and a new column added.

Evolution timeline

Changes between adjacent majors

PostgreSQL 18 ← 17Catalog added

+ name+ numa_node+ size

Compare any two versions

Pick two versions to see added, removed, and retyped columns. The interactive comparison needs JavaScript; the evolution timeline reads fine without it.