The default is TLSv1.2, which satisfies industry
best practices as of this writing.
+
+ This parameter can only be set in the postgresql.conf
+ file or on the server command line.
+
useful for testing or if some component has issues working with a
newer protocol.
+
+ This parameter can only be set in the postgresql.conf
+ file or on the server command line.
+
.
The default is zero (0).
When set to 0, the default huge page size on the
- system will be used.
+ system will be used. This parameter can only be set at server start.
Some commonly available page sizes on modern 64 bit server architectures include:
the value of should
be used instead. The setting has no effect on the behavior of
VACUUM when run in other contexts.
+ This parameter can only be set in the
+ postgresql.conf file or on the server command
+ line.
the huge_pages setting on operating systems where
that is supported, and may be more likely to benefit from larger pages
on operating systems where that is managed automatically.
- The default value is 0 (none).
+ The default value is 0 (none). This parameter can
+ only be set at server start.
max_worker_processes.
- The default value is 4.
+ The default value is 4. This parameter can only be set at server
+ start.
max_logical_replication_workers.
- The default value is 2.
+ The default value is 2. This parameter can only be set in the
+ postgresql.conf file or on the server command
+ line.
useful to disable the restart so that the clusterware can gain
control and take any actions it deems appropriate.
+
+ This parameter can only be set in the postgresql.conf
+ file or on the server command line.
+
retained and may be used for debugging, for example. Repeated crashes
may however result in accumulation of useless files.
+
+ This parameter can only be set in the postgresql.conf
+ file or on the server command line.
+
PostgreSQL, and relevant error messages may
appear only in kernel logs.
+ This parameter can only be set at server start.
+