-
+
Localization>
linkend="runtime-config-client-format"> for details). The defaults that are
chosen by initdb are actually only written into
the configuration file postgresql.conf to
- serve as defaults when the server is started. If you delete the
+ serve as defaults when the server is started. If you delete these
assignments from postgresql.conf then the
- server will inherit the settings from the execution environment.
+ server will inherit the settings from its execution environment.
Behavior>
- Locale support influences the following features:
+ The locale settings influence the following SQL features:
- Sort order in queries using ORDER BY>
+ Sort order in queries using ORDER BY> on textual data
+
+ The upper>, lower>, and initcap>
+ functions
+
+
+
The to_char> family of functions
allows you to store text in a variety of character sets, including
single-byte character sets such as the ISO 8859 series and
multiple-byte character sets such as
EUC> (Extended Unix
- Code), UTF8, and Mule internal code. All character sets can be
+ Code), UTF-8, and Mule internal code. All character sets can be
used transparently throughout the server. (If you use extension
functions from other sources, it depends on whether they wrote
their code correctly.) The default character set is selected while
can use instead of
if you prefer to type longer option strings.
If no option is
- given, SQL_ASCII> is used.
+ given, initdb> attempts to determine the appropriate
+ encoding to use based on the specified or default locale.