You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add possibility to mount a tmpfs volume to /dev/shm to avoid issues like
[this](docker-library/postgres#416). To achieve that
two new options were introduced:
* `enableShmVolume` to PostgreSQL manifest, to specify whether or not mount
this volume per database cluster
* `enable_shm_volume` to operator configuration, to specify whether or not mount
per operator.
The first one, `enableShmVolume` takes precedence to allow us to be more flexible.
Copy file name to clipboardExpand all lines: docs/reference/operator_parameters.md
+8
Original file line number
Diff line number
Diff line change
@@ -224,6 +224,14 @@ CRD-based configuration.
224
224
***set_memory_request_to_limit**
225
225
Set `memory_request` to `memory_limit` for all Postgres clusters (the default value is also increased). This prevents certain cases of memory overcommitment at the cost of overprovisioning memory and potential scheduling problems for containers with high memory limits due to the lack of memory on Kubernetes cluster nodes. This affects all containers (Postgres, Scalyr sidecar, and other sidecars). The default is `false`.
226
226
227
+
***enable_shm_volume**
228
+
Instruct operator to start any new database pod without limitations on shm
229
+
memory. If this option is enabled, to the target database pod will be mounted
230
+
a new tmpfs volume to remove shm memory limitation (see e.g. the [docker
231
+
issue](https://github.com/docker-library/postgres/issues/416)). This option
232
+
is global for an operator object, and can be overwritten by `enableShmVolume`
233
+
parameter from Postgres manifest. The default is `true`
234
+
227
235
## Operator timeouts
228
236
229
237
This set of parameters define various timeouts related to some operator
0 commit comments