-
+
Localization>
Locale support is automatically initialized when a database
cluster is created using initdb.
initdb will initialize the database cluster
- with the locale setting of its execution environment; so if your
- system is already set to use the locale that you want in your
- database cluster then there is nothing else you need to do. If
- you want to use a different locale (or you are not sure which
- locale your system is set to), you can tell
- initdb exactly which locale you want with the
- option . For example:
+ with the locale setting of its execution environment by default,
+ so if your system is already set to use the locale that you want
+ in your database cluster then there is nothing else you need to
+ do. If you want to use a different locale (or you are not sure
+ which locale your system is set to), you can instruct
+ initdb exactly which locale to use by
+ specifying the option. For example:
initdb --locale=sv_SE
- This example sets the locale to Swedish (sv>) as spoken in
- Sweden (SE>). Other possibilities might be
- en_US> (U.S. English) and fr_CA> (Canada,
- French). If more than one character set can be useful for a locale
- then the specifications look like this:
+ This example sets the locale to Swedish (sv>) as spoken
+ in Sweden (SE>). Other possibilities might be
+ en_US> (U.S. English) and fr_CA> (French
+ Canadian). If more than one character set can be useful for a
+ locale then the specifications look like this:
cs_CZ.ISO8859-2>. What locales are available under what
names on your system depends on what was provided by the operating
system vendor and what was installed.
The other locale categories can be changed as desired whenever the
server is running by setting the run-time configuration variables
that have the same name as the locale categories (see
- linkend="runtime-config"> for details). The defaults that are
+ 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
- Sort order in queries using <command>ORDER BY>
+ Sort order in queries using <literal>ORDER BY>
databases each with a different character set.
-
+ id="multibyte-charset-supported">
Supported Character Sets
Refer to for information about
the syntax of string literals, and to
- for information about available operators and functions.
+ for information about available operators and functions. The
+ database character set determines the character set used to store
+ textual values; for more information on character set support,
+ refer to .
encoding
- Character set encoding to use in the new database. Specify
+ Character set encoding to use in the new database. Specify
a string constant (e.g., 'SQL_ASCII'),
or an integer encoding number, or DEFAULT
- to use the default encoding.
+ to use the default encoding. The character sets supported by the
+
PostgreSQL server are described in
+ .
- Specifies the character encoding scheme to be used in this database.
+ Specifies the character encoding scheme to be used in this
+ database. The character sets supported by the
+
PostgreSQL server are described in
+ .
Selects the encoding of the template database. This will also
- be the default encoding of any database you create later, unless you
- override it there. The default is SQL_ASCII.
+ be the default encoding of any database you create later,
+ unless you override it there. The default is
+ SQL_ASCII. The character sets supported by
+ the
PostgreSQL server are described
+ in .
Sets the default locale for the database cluster. If this
option is not specified, the locale is inherited from the
- environment that initdb runs in.
+ environment that initdb runs in. Locale
+ support is described in .
Enables run-time assertion checks, which is a debugging aid to
- detect programming mistakes. This is only available if it was
- enabled during compilation. If so, the default is on.
+ detect programming mistakes. This option is only available if
+ assertions were enabled when
PostgreSQL> was
+ compiled. If so, the default is on.
Sets the number of shared buffers for use by the server
- processes. This value defaults to 64 buffers, where each
- buffer is 8 kB.
+ processes. The default value of this parameter is chosen
+ automatically by
initdb; refer to
+ linkend="runtime-config-resource-memory"> for more information.
- Sets a named run-time parameter. Consult for
- a list and descriptions. Most of the other command line
- options are in fact short forms of such a parameter
- assignment.
- multiple parameters.
+ Sets a named run-time parameter. The configuration parameters
+ supported by
PostgreSQL are
+ described in . Most of the
+ other command line options are in fact short forms of such a
+ parameter assignment.
+ to set multiple parameters.
Sets the debug level. The higher this value is set, the more
debugging output is written to the server log. Values are from
- 1 to 5.
+ 1 to 5.
Disables fsync calls for performance
improvement, at the risk of data corruption in event of a
- system crash. This option corresponds to setting
- fsync=false> in postgresql.conf>. Read the detailed
- documentation before using this!
+ system crash. Specifying this option is equivalent to
+ disabling the configuration
+ parameter. Read the detailed documentation before using this!
+
has the opposite effect
of this option.
Specifies the IP host name or address on which the
postmaster is to listen for TCP/IP
- connections from client applications. The value can also be
- a space-separated list of addresses, or *> to specify
- listening on all available interfaces. An empty value specifies
- not listening on any IP addresses, in which case only Unix-domain
- sockets can be used to connect to the postmaster.
- Defaults to listening only
- on localhost.
- This option is equivalent to setting listen_addresses> in
- postgresql.conf>.
+ connections from client applications. The value can also be a
+ space-separated list of addresses, or *> to specify
+ listening on all available interfaces. An empty value
+ specifies not listening on any IP addresses, in which case
+ only Unix-domain sockets can be used to connect to the
+ postmaster. Defaults to listening only on
+ localhost.
+ Specifying this option is equivalent to setting the
+ linkend="guc-listen-addresses">.
Allows remote clients to connect via TCP/IP (Internet domain)
connections. Without this option, only local connections are
accepted. This option is equivalent to setting
- <literal>listen_addresses> to *> in
+ <varname>listen_addresses> to *> in
postgresql.conf> or via
This option is deprecated since it does not allow access to the
- full functionality of <literal>listen_addresses>. It's usually
- better to set >listen_addresses> directly.
+ full functionality of <xref linkend="guc-listen-addresses">.
+ It's usually better to set >listen_addresses> directly.
- Enables secure connections using SSL. You must have compiled with SSL
- enabled to use this option.
+ Enables secure connections using
SSL.
+
PostgreSQL must have been compiled with
+ support for
SSL for this option to be
+ available. For more information on using
SSL,
+ refer to .
is required to be at least twice
. See for a discussion of
system resource requirements for large numbers of client
- connections.)
+ connections.) Specifying this option is equivalent to setting the
+ configuration parameter.