shared_memory_size_in_huge_pages

shared_memory_size_in_huge_pages shows the number of huge pages needed for the main shared memory area. It is read-only metadata in PG15–18, not a runtime tuning control.

Note

Fact — official short description: “Shows the number of huge pages needed for the main shared memory area.”

Identity

Type , Valueinteger: Upstream pg_settings type
Context , Valueinternal: Internal/preset and not user-settable
Unit , Value—: Raw unit
Range , Value-1 – 2147483647: Raw limits in the last observed version
Enum values , Value—: — for non-enum types
Category , ValuePreset Options: Upstream classification
Latest boot value , Value-1: -1

Lifecycle

Fact	Value
First observed	PG15
Present in	PG15–19 Beta 3
Removed in	No
Introduction commit	`43c1c4f65eab` — Introduce GUC shared_memory_size_in_huge_pages
Commit date	2021-09-21
Discussion	thread 1

Default history

Measured PG9.0–19 Beta 3 boot defaults
Versions	Raw `boot_val`	Unit	Human value
PG15–19 Beta 3	`-1`	—	-1

How it works

Shows the number of huge pages needed for the main shared memory area. It is read-only and cannot be changed with SET or configuration-file edits.

It estimates how many huge pages the main shared-memory segment needs and returns -1 when the platform cannot provide the estimate.

Interpret it with shared_memory_size, huge_pages, huge_pages_status. Applications and operations tooling may read shared_memory_size_in_huge_pages for capability or environment detection, but cannot SET it; cross-cluster comparisons must account for build, initdb, and current-database differences.

Tuning advice

Tip

Advice. These are workload-specific starting points and must be validated with measurements.

Workload	Guidance
OLTP	Not tunable. Record shared_memory_size_in_huge_pages as a deployment/capability fact; if it is unexpected, fix the binary, initdb, or database-creation process rather than trying SET.
OLAP	Not tunable. Use shared_memory_size_in_huge_pages to verify format, build, or resource assumptions on analytical nodes and keep every read/write candidate compatible.
Small nodes	Not tunable. Preserve it in inventory and incident reports; do not custom-build or rebuild merely to change it without a demonstrated compatibility need.

Pigsty

Values use the fixed 8-vCPU, 32-GiB, 100-GiB SSD fixture and render the current Pigsty templates for PG19 Beta 3; this does not assert current Pigsty support for that historical or beta release.

Template	Effective value	Versus upstream boot	Source expression
OLTP	Unmodified	—	—
OLAP	Unmodified	—	—
CRIT	Unmodified	—	—
TINY	Unmodified	—	—

Caution

Advice — pending human review. Fact from the current Pigsty template projection: OLTP: PG15–19 Beta 3 unmodified; OLAP: PG15–19 Beta 3 unmodified; CRIT: PG15–19 Beta 3 unmodified; TINY: PG15–19 Beta 3 unmodified. No Pigsty-specific rationale is inferred from an absent override.

Common pitfalls

Trying to change read-only shared_memory_size_in_huge_pages with SET or a configuration file.
Assuming every cluster, database, or vendor build reports the same value.
Ignoring the value in file-format or feature-compatibility checks.
Treating reported metadata as a performance target instead of an environment fact.

shared_memory_size · huge_pages · huge_pages_status · num_os_semaphores · max_connections · block_size