Commit188eda0

committed

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

1 parent8e27be4 commit188eda0Copy full SHA for 188eda0

File tree

+170

-170

lines changed

+170

-170

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.38 2003/08/31 17:32:18 petere Exp $ -->`
	`1`	`+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.39 2003/09/11 18:30:38 momjian Exp $ -->`
`2`	`2`
`3`	`3`	`<chapter id="charset">`
`4`	`4`	`<title>Localization</>`
`@@ -769,7 +769,7 @@ char *pg_encoding_to_char(int <replaceable>encoding_id</replaceable>);`
`769`	`769`
`770`	`770`	`<listitem>`
`771`	`771`	`<para>`
`772`		`-Using <command>SETCLIENT_ENCODING TO</command>.`
	`772`	`+Using <command>SETclient_encoding TO</command>.`
`773`	`773`
`774`	`774`	`Setting the client encoding can be done with this SQL command:`
`775`	`775`
`@@ -786,13 +786,13 @@ SET NAMES '<replaceable>value</>';`
`786`	`786`	`To query the current client encoding:`
`787`	`787`
`788`	`788`	`<programlisting>`
`789`		`-SHOWCLIENT_ENCODING;`
	`789`	`+SHOWclient_encoding;`
`790`	`790`	`</programlisting>`
`791`	`791`
`792`	`792`	`To return to the default encoding:`
`793`	`793`
`794`	`794`	`<programlisting>`
`795`		`-RESETCLIENT_ENCODING;`
	`795`	`+RESETclient_encoding;`
`796`	`796`	`</programlisting>`
`797`	`797`	`</para>`
`798`	`798`	`</listitem>`

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,5 @@`
`1`	`1`	`<!--`
`2`		`-$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.171 2003/09/1117:26:20 momjian Exp $`
	`2`	`+$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.172 2003/09/1118:30:38 momjian Exp $`
`3`	`3`	`PostgreSQL documentation`
`4`	`4`	`-->`
`5`	`5`
`@@ -3435,7 +3435,7 @@ substring('foobar' from 'o(.)b') <lineannotation>o</lineannotation>`
`3435`	`3435`
`3436`	`3436`	`<para>`
`3437`	`3437`	`Normally the flavor of RE being used is determined by`
`3438`		`- <varname>REGEX_FLAVOR</>.`
	`3438`	`+ <varname>regex_flavor</>.`
`3439`	`3439`	`However, this can be overridden by a <firstterm>director</> prefix.`
`3440`	`3440`	`If an RE of any flavor begins with <literal>***:</>,`
`3441`	`3441`	`the rest of the RE is taken as an ARE.`
`@@ -3762,7 +3762,7 @@ substring('foobar' from 'o(.)b') <lineannotation>o</lineannotation>`
`3762`	`3762`
`3763`	`3763`	`While these differences are unlikely to create a problem for most`
`3764`	`3764`	`applications, you can avoid them if necessary by`
`3765`		`- setting <varname>REGEX_FLAVOR</> to <literal>extended</>.`
	`3765`	`+ setting <varname>regex_flavor</> to <literal>extended</>.`
`3766`	`3766`	`</para>`
`3767`	`3767`	`</sect3>`
`3768`	`3768`

Lines changed: 2 additions & 2 deletions

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

Lines changed: 2 additions & 2 deletions

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

Comments

(0)