Fix inconsistent capitalization of "PL/pgSQL".

Josh Kupershmidt

src/pl/plpgsql/src/gram.y

@@ -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
  * unrecognized keyword is the beginning of a SQL statement. This
  * 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,
  * we run the strings we expect to be SQL statements through the main
  * SQL parser.
@@ -3071,7 +3071,7 @@ make_scalar_list1(char *initial_name,
  * any database access and does not check any semantic rules, it just
  * checks for basic syntactic correctness. We do this here, rather
  * 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.
  *
  * It is assumed that "stmt" represents a copy of the function source text

src/pl/plpgsql/src/pl_comp.c

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

src/pl/plpgsql/src/pl_exec.c

@@ -2064,7 +2064,7 @@ static int
 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
 	 * the work will be done at the top level.
 	 */

src/test/regress/expected/plpgsql.out

@@ -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)
 --
 -- 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

src/test/regress/sql/plpgsql.sql

@@ -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;
--- they merely exercise specific parts of PL/PgSQL
+-- they merely exercise specific parts of PL/pgSQL
 --
 
 --