rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix inconsistent capitalization of "PL/pgSQL". 

Josh Kupershmidt
This commit is contained in:
Robert Haas 2010-09-22 21:57:37 -04:00
parent 8687fbbe42
commit 0c8ed2dafb
15 changed files with 37 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/external-projects.sgml
View File

@ -145,7 +145,7 @@
<para> <para>
<productname>PostgreSQL</productname> includes several procedural <productname>PostgreSQL</productname> includes several procedural
languages with the base distribution: <link languages with the base distribution: <link
linkend="plpgsql">PL/PgSQL</link>, <link linkend="pltcl">PL/Tcl</link>, linkend="plpgsql">PL/pgSQL</link>, <link linkend="pltcl">PL/Tcl</link>,
<link linkend="plperl">PL/Perl</link>, and <link <link linkend="plperl">PL/Perl</link>, and <link
linkend="plpython">PL/Python</link>. linkend="plpython">PL/Python</link>.
</para> </para>

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

@ -1139,17 +1139,17 @@ EXECUTE 'SELECT count(*) FROM '
<indexterm> <indexterm>
<primary>quote_ident</primary> <primary>quote_ident</primary>
<secondary>use in PL/PgSQL</secondary> <secondary>use in PL/pgSQL</secondary>
</indexterm> </indexterm>
<indexterm> <indexterm>
<primary>quote_literal</primary> <primary>quote_literal</primary>
<secondary>use in PL/PgSQL</secondary> <secondary>use in PL/pgSQL</secondary>
</indexterm> </indexterm>
<indexterm> <indexterm>
<primary>quote_nullable</primary> <primary>quote_nullable</primary>
<secondary>use in PL/PgSQL</secondary> <secondary>use in PL/pgSQL</secondary>
</indexterm> </indexterm>
<para> <para>
@ -1492,11 +1492,11 @@ RETURN <replaceable>expression</replaceable>;
<title><command>RETURN NEXT</> and <command>RETURN QUERY</command></title> <title><command>RETURN NEXT</> and <command>RETURN QUERY</command></title>
<indexterm> <indexterm>
<primary>RETURN NEXT</primary> <primary>RETURN NEXT</primary>
<secondary>in PL/PgSQL</secondary> <secondary>in PL/pgSQL</secondary>
</indexterm> </indexterm>
<indexterm> <indexterm>
<primary>RETURN QUERY</primary> <primary>RETURN QUERY</primary>
<secondary>in PL/PgSQL</secondary> <secondary>in PL/pgSQL</secondary>
</indexterm> </indexterm>
<synopsis> <synopsis>
@ -2220,7 +2220,7 @@ END LOOP <optional> <replaceable>label</replaceable> </optional>;
<indexterm> <indexterm>
<primary>exceptions</primary> <primary>exceptions</primary>
<secondary>in PL/PgSQL</secondary> <secondary>in PL/pgSQL</secondary>
</indexterm> </indexterm>
<para> <para>
@ -2898,7 +2898,7 @@ END LOOP <optional> <replaceable>label</replaceable> </optional>;
<indexterm> <indexterm>
<primary>reporting errors</primary> <primary>reporting errors</primary>
<secondary>in PL/PgSQL</secondary> <secondary>in PL/pgSQL</secondary>
</indexterm> </indexterm>
<para> <para>

2
doc/src/sgml/release-7.4.sgml
View File

@ -1897,7 +1897,7 @@ enabled</para></listitem>
files during postmaster startup</para></listitem> files during postmaster startup</para></listitem>
<listitem><para>Various memory leakage fixes</para></listitem> <listitem><para>Various memory leakage fixes</para></listitem>
<listitem><para>Various portability improvements</para></listitem> <listitem><para>Various portability improvements</para></listitem>
<listitem><para>Fix PL/PgSQL to handle <literal>var := var</> correctly when <listitem><para>Fix PL/pgSQL to handle <literal>var := var</> correctly when
the variable is of pass-by-reference type</para></listitem> the variable is of pass-by-reference type</para></listitem>
<listitem><para>Update <filename>contrib/tsearch2</> to use current Snowball <listitem><para>Update <filename>contrib/tsearch2</> to use current Snowball
code</para></listitem> code</para></listitem>

2
doc/src/sgml/release-8.0.sgml
View File

@ -2512,7 +2512,7 @@ when opening the file fails</para></listitem>
constraints more reliably</para></listitem> constraints more reliably</para></listitem>
<listitem><para>Fix password prompting in <application>pg_restore</> on <listitem><para>Fix password prompting in <application>pg_restore</> on
Windows</para></listitem> Windows</para></listitem>
<listitem><para>Fix PL/PgSQL to handle <literal>var := var</> correctly when <listitem><para>Fix PL/pgSQL to handle <literal>var := var</> correctly when
the variable is of pass-by-reference type</para></listitem> the variable is of pass-by-reference type</para></listitem>
<listitem><para>Fix PL/Perl <literal>%_SHARED</> so it's actually <listitem><para>Fix PL/Perl <literal>%_SHARED</> so it's actually
shared</para></listitem> shared</para></listitem>

10
doc/src/sgml/release-8.1.sgml
View File

@ -1212,7 +1212,7 @@
<listitem> <listitem>
<para> <para>
Fix PL/PgSQL to not fail when a <literal>FOR</> loop's target variable Fix PL/pgSQL to not fail when a <literal>FOR</> loop's target variable
is a record containing composite-type fields (Tom) is a record containing composite-type fields (Tom)
</para> </para>
</listitem> </listitem>
@ -4343,7 +4343,7 @@ SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';
<listitem> <listitem>
<para> <para>
Allow SQL and PL/PgSQL functions to use <command>OUT</> and Allow SQL and PL/pgSQL functions to use <command>OUT</> and
<command>INOUT</> parameters (Tom) <command>INOUT</> parameters (Tom)
</para> </para>
<para> <para>
@ -4378,12 +4378,12 @@ SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';
</sect3> </sect3>
<sect3> <sect3>
<title>PL/PgSQL Server-Side Language Changes</title> <title>PL/pgSQL Server-Side Language Changes</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Overhaul the memory management of PL/PgSQL functions (Neil) Overhaul the memory management of PL/pgSQL functions (Neil)
</para> </para>
<para> <para>
The parsetree of each function is now stored in a separate The parsetree of each function is now stored in a separate
@ -4426,7 +4426,7 @@ SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';
<listitem> <listitem>
<para> <para>
Add support for an optional <command>INTO</> clause to Add support for an optional <command>INTO</> clause to
PL/PgSQL's <command>EXECUTE</> statement (Pavel Stehule, Neil) PL/pgSQL's <command>EXECUTE</> statement (Pavel Stehule, Neil)
</para> </para>
</listitem> </listitem>

6
doc/src/sgml/release-8.2.sgml
View File

@ -1661,7 +1661,7 @@
<listitem> <listitem>
<para> <para>
Fix PL/PgSQL to not fail when a <literal>FOR</> loop's target variable Fix PL/pgSQL to not fail when a <literal>FOR</> loop's target variable
is a record containing composite-type fields (Tom) is a record containing composite-type fields (Tom)
</para> </para>
</listitem> </listitem>
@ -4883,7 +4883,7 @@
</sect3> </sect3>
<sect3> <sect3>
<title>PL/PgSQL Server-Side Language Changes</title> <title>PL/pgSQL Server-Side Language Changes</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -5448,7 +5448,7 @@
linkend="guc-local-preload-libraries"><varname>local_preload_libraries</></link> linkend="guc-local-preload-libraries"><varname>local_preload_libraries</></link>
that allows libraries to be loaded into specific sessions without that allows libraries to be loaded into specific sessions without
explicit cooperation from the client application. This allows explicit cooperation from the client application. This allows
external add-ons to implement features such as a PL/PgSQL debugger. external add-ons to implement features such as a PL/pgSQL debugger.
</para> </para>
</listitem> </listitem>

14
doc/src/sgml/release-8.3.sgml
View File

@ -2239,7 +2239,7 @@
<listitem> <listitem>
<para> <para>
Fix PL/PgSQL to not fail when a <literal>FOR</> loop's target variable Fix PL/pgSQL to not fail when a <literal>FOR</> loop's target variable
is a record containing composite-type fields (Tom) is a record containing composite-type fields (Tom)
</para> </para>
</listitem> </listitem>
@ -3914,7 +3914,7 @@ current_date &lt; 2017-11-17
</para> </para>
<para> <para>
Previously PL/PgSQL functions that referenced temporary tables Previously PL/pgSQL functions that referenced temporary tables
would fail if the temporary table was dropped and recreated would fail if the temporary table was dropped and recreated
between function invocations, unless <literal>EXECUTE</> was between function invocations, unless <literal>EXECUTE</> was
used. This improvement fixes that problem and many related issues. used. This improvement fixes that problem and many related issues.
@ -4740,7 +4740,7 @@ current_date &lt; 2017-11-17
The first request for statistics in a transaction takes a statistics The first request for statistics in a transaction takes a statistics
snapshot that does not change during the transaction. This function snapshot that does not change during the transaction. This function
allows the snapshot to be discarded and a new snapshot loaded during allows the snapshot to be discarded and a new snapshot loaded during
the next statistics query. This is particularly useful for PL/PgSQL the next statistics query. This is particularly useful for PL/pgSQL
functions, which are confined to a single transaction. functions, which are confined to a single transaction.
</para> </para>
</listitem> </listitem>
@ -4835,7 +4835,7 @@ current_date &lt; 2017-11-17
</sect3> </sect3>
<sect3> <sect3>
<title>PL/PgSQL Server-Side Language</title> <title>PL/pgSQL Server-Side Language</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -4848,7 +4848,7 @@ current_date &lt; 2017-11-17
<listitem> <listitem>
<para> <para>
Allow <literal>IN</literal> as an alternative to Allow <literal>IN</literal> as an alternative to
<literal>FROM</literal> in PL/PgSQL's <command>FETCH</command> <literal>FROM</literal> in PL/pgSQL's <command>FETCH</command>
statement, for consistency with the backend's statement, for consistency with the backend's
<command>FETCH</command> command (Pavel Stehule) <command>FETCH</command> command (Pavel Stehule)
</para> </para>
@ -4856,7 +4856,7 @@ current_date &lt; 2017-11-17
<listitem> <listitem>
<para> <para>
Add <command>MOVE</command> to PL/PgSQL (Magnus, Pavel Stehule, Add <command>MOVE</command> to PL/pgSQL (Magnus, Pavel Stehule,
Neil) Neil)
</para> </para>
</listitem> </listitem>
@ -4867,7 +4867,7 @@ current_date &lt; 2017-11-17
</para> </para>
<para> <para>
This adds convenient syntax for PL/PgSQL set-returning functions This adds convenient syntax for PL/pgSQL set-returning functions
that want to return the result of a query. <command>RETURN QUERY</> that want to return the result of a query. <command>RETURN QUERY</>
is easier and more efficient than a loop is easier and more efficient than a loop
around <command>RETURN NEXT</command>. around <command>RETURN NEXT</command>.

4
doc/src/sgml/release-8.4.sgml
View File

@ -2689,7 +2689,7 @@ WITH w AS (SELECT * FROM foo) SELECT * FROM w, bar ... FOR UPDATE
</para> </para>
<para> <para>
In particular, this means that functions written in PL/PgSQL In particular, this means that functions written in PL/pgSQL
and other PL languages can now be called this way. and other PL languages can now be called this way.
</para> </para>
</listitem> </listitem>
@ -3815,7 +3815,7 @@ WITH w AS (SELECT * FROM foo) SELECT * FROM w, bar ... FOR UPDATE
</sect4> </sect4>
<sect4> <sect4>
<title>PL/PgSQL Server-Side Language</title> <title>PL/pgSQL Server-Side Language</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>

2
doc/src/sgml/release-9.0.sgml
View File

@ -1948,7 +1948,7 @@
</itemizedlist> </itemizedlist>
<sect4> <sect4>
<title><link linkend="plpgsql">PL/PgSQL</link> Server-Side <title><link linkend="plpgsql">PL/pgSQL</link> Server-Side
Language</title> Language</title>
<itemizedlist> <itemizedlist>

2
doc/src/sgml/release-old.sgml
View File

@ -692,7 +692,7 @@ pages</para></listitem>
enabled</para></listitem> enabled</para></listitem>
<listitem><para>Various memory leakage fixes</para></listitem> <listitem><para>Various memory leakage fixes</para></listitem>
<listitem><para>Various portability improvements</para></listitem> <listitem><para>Various portability improvements</para></listitem>
<listitem><para>Fix PL/PgSQL to handle <literal>var := var</> correctly when <listitem><para>Fix PL/pgSQL to handle <literal>var := var</> correctly when
the variable is of pass-by-reference type</para></listitem> the variable is of pass-by-reference type</para></listitem>
</itemizedlist> </itemizedlist>

6
src/pl/plpgsql/src/gram.y
View File

@ -3058,11 +3058,11 @@ make_scalar_list1(char *initial_name,
} }
/* /*
* When the PL/PgSQL parser expects to see a SQL statement, it is very * When the PL/pgSQL parser expects to see a SQL statement, it is very
* liberal in what it accepts; for example, we often assume an * liberal in what it accepts; for example, we often assume an
* unrecognized keyword is the beginning of a SQL statement. This * unrecognized keyword is the beginning of a SQL statement. This
* avoids the need to duplicate parts of the SQL grammar in the * avoids the need to duplicate parts of the SQL grammar in the
* PL/PgSQL grammar, but it means we can accept wildly malformed * PL/pgSQL grammar, but it means we can accept wildly malformed
* input. To try and catch some of the more obviously invalid input, * input. To try and catch some of the more obviously invalid input,
* we run the strings we expect to be SQL statements through the main * we run the strings we expect to be SQL statements through the main
* SQL parser. * SQL parser.
@ -3071,7 +3071,7 @@ make_scalar_list1(char *initial_name,
* any database access and does not check any semantic rules, it just * any database access and does not check any semantic rules, it just
* checks for basic syntactic correctness. We do this here, rather * checks for basic syntactic correctness. We do this here, rather
* than after parsing has finished, because a malformed SQL statement * than after parsing has finished, because a malformed SQL statement
* may cause the PL/PgSQL parser to become confused about statement * may cause the PL/pgSQL parser to become confused about statement
* borders. So it is best to bail out as early as we can. * borders. So it is best to bail out as early as we can.
* *
* It is assumed that "stmt" represents a copy of the function source text * It is assumed that "stmt" represents a copy of the function source text

4
src/pl/plpgsql/src/pl_comp.c
View File

@ -336,7 +336,7 @@ do_compile(FunctionCallInfo fcinfo,
* per-function memory context, so it can be reclaimed easily. * per-function memory context, so it can be reclaimed easily.
*/ */
func_cxt = AllocSetContextCreate(TopMemoryContext, func_cxt = AllocSetContextCreate(TopMemoryContext,
"PL/PgSQL function context", "PL/pgSQL function context",
ALLOCSET_DEFAULT_MINSIZE, ALLOCSET_DEFAULT_MINSIZE,
ALLOCSET_DEFAULT_INITSIZE, ALLOCSET_DEFAULT_INITSIZE,
ALLOCSET_DEFAULT_MAXSIZE); ALLOCSET_DEFAULT_MAXSIZE);
@ -768,7 +768,7 @@ plpgsql_compile_inline(char *proc_source)
* its own memory context, so it can be reclaimed easily. * its own memory context, so it can be reclaimed easily.
*/ */
func_cxt = AllocSetContextCreate(CurrentMemoryContext, func_cxt = AllocSetContextCreate(CurrentMemoryContext,
"PL/PgSQL function context", "PL/pgSQL function context",
ALLOCSET_DEFAULT_MINSIZE, ALLOCSET_DEFAULT_MINSIZE,
ALLOCSET_DEFAULT_INITSIZE, ALLOCSET_DEFAULT_INITSIZE,
ALLOCSET_DEFAULT_MAXSIZE); ALLOCSET_DEFAULT_MAXSIZE);

2
src/pl/plpgsql/src/pl_exec.c
View File

@ -2064,7 +2064,7 @@ static int
exec_stmt_return(PLpgSQL_execstate *estate, PLpgSQL_stmt_return *stmt) exec_stmt_return(PLpgSQL_execstate *estate, PLpgSQL_stmt_return *stmt)
{ {
/* /*
* If processing a set-returning PL/PgSQL function, the final RETURN * If processing a set-returning PL/pgSQL function, the final RETURN
* indicates that the function is finished producing tuples. The rest of * indicates that the function is finished producing tuples. The rest of
* the work will be done at the top level. * the work will be done at the top level.
*/ */

2
src/test/regress/expected/plpgsql.out
View File

@ -1541,7 +1541,7 @@ insert into IFace values ('IF', 'orion', 'ethernet_interface_name_too_long', '')
ERROR: IFace slotname "IF.orion.ethernet_interface_name_too_long" too long (20 char max) ERROR: IFace slotname "IF.orion.ethernet_interface_name_too_long" too long (20 char max)
-- --
-- The following tests are unrelated to the scenario outlined above; -- The following tests are unrelated to the scenario outlined above;
-- they merely exercise specific parts of PL/PgSQL -- they merely exercise specific parts of PL/pgSQL
-- --
-- --
-- Test recursion, per bug report 7-Sep-01 -- Test recursion, per bug report 7-Sep-01

2
src/test/regress/sql/plpgsql.sql
View File

@ -1420,7 +1420,7 @@ insert into IFace values ('IF', 'orion', 'ethernet_interface_name_too_long', '')
-- --
-- The following tests are unrelated to the scenario outlined above; -- The following tests are unrelated to the scenario outlined above;
-- they merely exercise specific parts of PL/PgSQL -- they merely exercise specific parts of PL/pgSQL
-- --
-- --