Reports the state of huge pages in the current instance: on, off, or unknown (if displayed with postgres -C).
At a glance
| Property | Value |
|---|---|
| Parameter | huge_pages_status |
| Category | Preset Options |
| Default | (see documentation) |
| Value type | enum |
| Change scope | Per-session (SET) |
| Available in | PostgreSQL 17, 18, 19 (added in 17) |
What it does
Reports the state of huge pages in the current instance: on, off, or unknown (if displayed with postgres -C). This parameter is useful to determine whether allocation of huge pages was successful under huge_pages=try. See huge_pages for more information.
(Description quoted from the official PostgreSQL documentation.)
How to apply a change
Can be set per session with SET, per role/database with ALTER ROLE/DATABASE ... SET, or globally in postgresql.conf.
Inspect the current value and source with SHOW huge_pages_status; or SELECT name, setting, unit, context, source FROM pg_settings WHERE name = 'huge_pages_status';.
Tuning guidance
This is a preset, read-only parameter: it reports a value fixed when PostgreSQL was built or the cluster was initialized, and cannot be tuned at runtime. Read it to verify the server’s build or cluster configuration (for example when matching a replica or debugging a compatibility issue); there is no setting to adjust.