mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix a couple of places that still claimed LC_COLLATE and LC_CTYPE can't

Browse Source 
be changed after initdb.
This commit is contained in:
Tom Lane 2009-03-26 20:55:49 +00:00
parent b793e8344a
commit 845693f70f
2 changed files with 29 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/src/sgml/charset.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.91 2009/02/10 19:29:39 petere Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.92 2009/03/26 20:55:49 tgl Exp $ -->
<chapter id="charset"> <chapter id="charset">
<title>Localization</> <title>Localization</>
@ -136,18 +136,18 @@ initdb --locale=sv_SE
and <literal>LC_CTYPE</literal> are those categories. They affect and <literal>LC_CTYPE</literal> are those categories. They affect
the sort order of indexes, so they must be kept fixed, or indexes on the sort order of indexes, so they must be kept fixed, or indexes on
text columns will become corrupt. The default values for these text columns will become corrupt. The default values for these
categories are defined when <command>initdb</command> is run, and categories are determined when <command>initdb</command> is run, and
those values are used when new databases are created, unless those values are used when new databases are created, unless
specified otherwise in the <command>CREATE DATABASE</command> command. specified otherwise in the <command>CREATE DATABASE</command> command.
</para> </para>
<para> <para>
The other locale categories can be changed as desired whenever the The other locale categories can be changed whenever desired
server is running by setting the run-time configuration variables by setting the server configuration parameters
that have the same name as the locale categories (see <xref that have the same name as the locale categories (see <xref
linkend="runtime-config-client-format"> for details). The defaults linkend="runtime-config-client-format"> for details). The values
that are chosen by <command>initdb</command> are actually only written into that are chosen by <command>initdb</command> are actually only written
the configuration file <filename>postgresql.conf</filename> to into the configuration file <filename>postgresql.conf</filename> to
serve as defaults when the server is started. If you delete these serve as defaults when the server is started. If you delete these
assignments from <filename>postgresql.conf</filename> then the assignments from <filename>postgresql.conf</filename> then the
server will inherit the settings from its execution environment. server will inherit the settings from its execution environment.
@ -200,7 +200,8 @@ initdb --locale=sv_SE
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Sort order in queries using <literal>ORDER BY</> on textual data Sort order in queries using <literal>ORDER BY</> or the standard
comparison operators on textual data
<indexterm><primary>ORDER BY</><secondary>and locales</></indexterm> <indexterm><primary>ORDER BY</><secondary>and locales</></indexterm>
</para> </para>
</listitem> </listitem>
@ -261,9 +262,9 @@ initdb --locale=sv_SE
<para> <para>
Check that <productname>PostgreSQL</> is actually using the locale Check that <productname>PostgreSQL</> is actually using the locale
that you think it is. The default <envar>LC_COLLATE</> and <envar>LC_CTYPE</> that you think it is. The <envar>LC_COLLATE</> and <envar>LC_CTYPE</>
settings are determined at <command>initdb</> time and cannot be settings are determined when a database is created, and cannot be
changed without repeating <command>initdb</>. Other locale changed except by creating a new database. Other locale
settings including <envar>LC_MESSAGES</> and <envar>LC_MONETARY</> settings including <envar>LC_MESSAGES</> and <envar>LC_MONETARY</>
are initially determined by the environment the server is started are initially determined by the environment the server is started
in, but can be changed on-the-fly. You can check the active locale in, but can be changed on-the-fly. You can check the active locale

6
doc/src/sgml/config.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.212 2009/03/23 15:14:14 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.213 2009/03/26 20:55:49 tgl Exp $ -->
<chapter Id="runtime-config"> <chapter Id="runtime-config">
<title>Server Configuration</title> <title>Server Configuration</title>
@ -4880,7 +4880,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
<para> <para>
Reports the locale in which sorting of textual data is done. Reports the locale in which sorting of textual data is done.
See <xref linkend="locale"> for more information. See <xref linkend="locale"> for more information.
The value is determined when the database cluster is initialized. This value is determined when a database is created.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -4894,7 +4894,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
<para> <para>
Reports the locale that determines character classifications. Reports the locale that determines character classifications.
See <xref linkend="locale"> for more information. See <xref linkend="locale"> for more information.
The value is determined when the database cluster is initialized. This value is determined when a database is created.
Ordinarily this will be the same as <varname>lc_collate</varname>, Ordinarily this will be the same as <varname>lc_collate</varname>,
but for special applications it might be set differently. but for special applications it might be set differently.
</para> </para>