Skip to content

Commit 760679a

Browse files
authored
Merge pull request #6858 from EnterpriseDB/content/docs/postgres_tuner/add_parameter/docs-1555
Postgres Tuner - Added a parameter
2 parents e070ce0 + 315cd33 commit 760679a

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

advocacy_docs/pg_extensions/pg_tuner/configuring.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,8 @@ The following custom GUCs control the EDB Postgres Tuner `work_mem` tuning behav
4343

4444
- `edb_pg_tuner.buffer_size` — Maximum query count for tracking statistics. The default is 5000.
4545

46+
- `edb_pg_tuner.container_memory_limit_file_path` — Specifies the path to the file that contains the memory limit set by the container runtime, such as Docker or Kubernetes. This file is read by `edb_pg_tuner` to determine the maximum amount of memory available to the database process when running inside a container. Based on this limit, the tuner can generate optimised PostgreSQL configuration recommendations that are container-aware. The file is at `/sys/fs/cgroup/memory/memory.limit_in_bytes` by default.
47+
4648
## Recommended GUCs
4749

4850
EDB Postgres Tuner can recommend the following GUCs. The `static` category provides fixed recommendation settings. The `dynamic` category uses specific algorithms to suggest a better setting according to your workload or hardware resources.

0 commit comments

Comments
 (0)