database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-27 22:56:53 +03:00
Code

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
Show Stats 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"> <chapter id="charset">
<title>Localization</> <title>Localization</>
@ -769,7 +769,7 @@ char *pg_encoding_to_char(int <replaceable>encoding_id</replaceable>);
<listitem> <listitem>
<para> <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: 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: To query the current client encoding:
<programlisting> <programlisting>
SHOW CLIENT_ENCODING; SHOW client_encoding;
</programlisting> </programlisting>
To return to the default encoding: To return to the default encoding:
<programlisting> <programlisting>
RESET CLIENT_ENCODING; RESET client_encoding;
</programlisting> </programlisting>
</para> </para>
</listitem> </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 PostgreSQL documentation
--> -->
@ -3435,7 +3435,7 @@ substring('foobar' from 'o(.)b') <lineannotation>o</lineannotation>
<para> <para>
Normally the flavor of RE being used is determined by 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. However, this can be overridden by a <firstterm>director</> prefix.
If an RE of any flavor begins with <literal>***:</>, If an RE of any flavor begins with <literal>***:</>,
the rest of the RE is taken as an ARE. 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 While these differences are unlikely to create a problem for most
applications, you can avoid them if necessary by applications, you can avoid them if necessary by
setting <varname>REGEX_FLAVOR</> to <literal>extended</>. setting <varname>regex_flavor</> to <literal>extended</>.
</para> </para>
</sect3> </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"> <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 <productname>PostgreSQL</productname> planner will switch from exhaustive
search to a <firstterm>genetic</firstterm> probabilistic search search to a <firstterm>genetic</firstterm> probabilistic search
through a limited number of possibilities. (The switch-over threshold is 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.) parameter.)
The genetic search takes less time, but it won't The genetic search takes less time, but it won't
necessarily find the best possible plan. 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"> <chapter id="plpgsql">
@ -1350,7 +1350,7 @@ SELECT * FROM some_func();
allow users to allow users to define set-returning functions allow users to allow users to define set-returning functions
that do not have this limitation. Currently, the point at that do not have this limitation. Currently, the point at
which data begins being written to disk is controlled by the 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 who have sufficient memory to store larger result sets in
memory should consider increasing this parameter. memory should consider increasing this parameter.
</para> </para>

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

File diff suppressed because it is too large Load Diff

4
src/backend/postmaster/postmaster.c
View File

@ -37,7 +37,7 @@
* *
* *
* IDENTIFICATION * IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/postmaster/postmaster.c,v 1.343 2003/09/04 03:38:55 momjian Exp $ * $Header: /cvsroot/pgsql/src/backend/postmaster/postmaster.c,v 1.344 2003/09/11 18:30:39 momjian Exp $
* *
* NOTES * NOTES
* *
@ -2609,7 +2609,7 @@ sigusr1_handler(SIGNAL_ARGS)
ereport(LOG, ereport(LOG,
(errmsg("checkpoints are occurring too frequently (%d seconds apart)", (errmsg("checkpoints are occurring too frequently (%d seconds apart)",
elapsed_secs), elapsed_secs),
errhint("Consider increasing CHECKPOINT_SEGMENTS."))); errhint("Consider increasing 'checkpoint_segments'.")));
} }
LastSignalledCheckpoint = now; LastSignalledCheckpoint = now;
} }

4
src/backend/utils/misc/guc.c
View File

@ -10,7 +10,7 @@
* Written by Peter Eisentraut <peter_e@gmx.net>. * Written by Peter Eisentraut <peter_e@gmx.net>.
* *
* IDENTIFICATION * IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.156 2003/09/07 15:26:53 tgl Exp $ * $Header: /cvsroot/pgsql/src/backend/utils/misc/guc.c,v 1.157 2003/09/11 18:30:39 momjian Exp $
* *
*-------------------------------------------------------------------- *--------------------------------------------------------------------
*/ */
@ -1311,7 +1311,7 @@ static struct config_string ConfigureNamesString[] =
{ {
{"log_error_verbosity", PGC_SUSET, LOGGING_WHEN, {"log_error_verbosity", PGC_SUSET, LOGGING_WHEN,
gettext_noop("Controls verbosity of logged messages"), gettext_noop("Controls verbosity of logged messages"),
gettext_noop("Valid values are TERSE, DEFAULT, and VERBOSE") gettext_noop("Valid values are 'terse', 'default', and 'verbose'")
}, },
&log_error_verbosity_str, &log_error_verbosity_str,
"default", assign_log_error_verbosity, NULL "default", assign_log_error_verbosity, NULL