database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Consistenly lowercase GUC variable names, in docs and error messages.

Browse Source
This commit is contained in:
Bruce Momjian
2003-09-11 18:30:39 +00:00
parent 8e27be4310
commit 188eda0df2
7 changed files with 170 additions and 170 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,4 +1,4 @@
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.38 2003/08/31 17:32:18 petere Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.39 2003/09/11 18:30:38 momjian Exp $ -->
<chapter id="charset">
<title>Localization</>
@ -769,7 +769,7 @@ char *pg_encoding_to_char(int <replaceable>encoding_id</replaceable>);
<listitem>
<para>
Using <command>SET CLIENT_ENCODING TO</command>.
Using <command>SET client_encoding TO</command>.
Setting the client encoding can be done with this SQL command:
@ -786,13 +786,13 @@ SET NAMES '<replaceable>value</>';
To query the current client encoding:
<programlisting>
SHOW CLIENT_ENCODING;
SHOW client_encoding;
</programlisting>
To return to the default encoding:
<programlisting>
RESET CLIENT_ENCODING;
RESET client_encoding;
</programlisting>
</para>
</listitem>

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

@ -1,5 +1,5 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.171 2003/09/11 17:26:20 momjian Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.172 2003/09/11 18:30:38 momjian Exp $
PostgreSQL documentation
-->
@ -3435,7 +3435,7 @@ substring('foobar' from 'o(.)b') <lineannotation>o</lineannotation>
<para>
Normally the flavor of RE being used is determined by
<varname>REGEX_FLAVOR</>.
<varname>regex_flavor</>.
However, this can be overridden by a <firstterm>director</> prefix.
If an RE of any flavor begins with <literal>***:</>,
the rest of the RE is taken as an ARE.
@ -3762,7 +3762,7 @@ substring('foobar' from 'o(.)b') <lineannotation>o</lineannotation>
While these differences are unlikely to create a problem for most
applications, you can avoid them if necessary by
setting <varname>REGEX_FLAVOR</> to <literal>extended</>.
setting <varname>regex_flavor</> to <literal>extended</>.
</para>
</sect3>

4
doc/src/sgml/perform.sgml
View File

@ -1,5 +1,5 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.32 2003/09/11 17:31:45 momjian Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.33 2003/09/11 18:30:38 momjian Exp $
-->
<chapter id="performance-tips">
@ -603,7 +603,7 @@ SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id;
<productname>PostgreSQL</productname> planner will switch from exhaustive
search to a <firstterm>genetic</firstterm> probabilistic search
through a limited number of possibilities. (The switch-over threshold is
set by the <varname>GEQO_THRESHOLD</varname> run-time
set by the <varname>geqo_threshold</varname> run-time
parameter.)
The genetic search takes less time, but it won't
necessarily find the best possible plan.

4
doc/src/sgml/plpgsql.sgml
View File

@ -1,5 +1,5 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/plpgsql.sgml,v 1.23 2003/09/11 17:31:45 momjian Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/plpgsql.sgml,v 1.24 2003/09/11 18:30:38 momjian Exp $
-->
<chapter id="plpgsql">
@ -1350,7 +1350,7 @@ SELECT * FROM some_func();
allow users to allow users to define set-returning functions
that do not have this limitation. Currently, the point at
which data begins being written to disk is controlled by the
<varname>SORT_MEM</> configuration variable. Administrators
<varname>sort_mem</> configuration variable. Administrators
who have sufficient memory to store larger result sets in
memory should consider increasing this parameter.
</para>

310
doc/src/sgml/runtime.sgml
View File

File diff suppressed because it is too large Load Diff