From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/config-setting.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/config-setting.html') diff --git a/doc/src/sgml/html/config-setting.html b/doc/src/sgml/html/config-setting.html index a5d68b7..06f6339 100644 --- a/doc/src/sgml/html/config-setting.html +++ b/doc/src/sgml/html/config-setting.html @@ -1,5 +1,5 @@ -20.1. Setting Parameters
20.1. Setting Parameters
Prev UpChapter 20. Server ConfigurationHome Next

20.1. Setting Parameters

20.1.1. Parameter Names and Values
20.1.2. Parameter Interaction via the Configuration File
20.1.3. Parameter Interaction via SQL
20.1.4. Parameter Interaction via the Shell
20.1.5. Managing Configuration File Contents

20.1.1. Parameter Names and Values

+20.1. Setting Parameters

20.1. Setting Parameters
Prev UpChapter 20. Server ConfigurationHome Next

20.1. Setting Parameters

20.1.1. Parameter Names and Values
20.1.2. Parameter Interaction via the Configuration File
20.1.3. Parameter Interaction via SQL
20.1.4. Parameter Interaction via the Shell
20.1.5. Managing Configuration File Contents

20.1.1. Parameter Names and Values

All parameter names are case-insensitive. Every parameter takes a value of one of five types: boolean, string, integer, floating point, or enumerated (enum). The type determines the syntax for setting the @@ -333,4 +333,4 @@ include_dir 'conf.d' their configurations all stored in one place, such as in a version control repository. (Storing database configuration files under version control is another good practice to consider.) -

Prev Up Next
Chapter 20. Server Configuration Home 20.2. File Locations
\ No newline at end of file +

Prev Up Next
Chapter 20. Server Configuration Home 20.2. File Locations
\ No newline at end of file -- cgit v1.2.3