Code review for escape-strings patch. Sync psql and plpgsql lexers

with main, avoid using a SQL-defined SQLSTATE for what is most definitely
not a SQL-compatible error condition, fix documentation omissions,
adhere to message style guidelines, don't use two GUC_REPORT variables
when one is sufficient.  Nothing done about pg_dump issues.

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml
index 3d8d457c56..0d3d7f19f1 100644
--- a/doc/src/sgml/syntax.sgml
+++ b/doc/src/sgml/syntax.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.101 2005/06/26 03:03:21 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.102 2005/06/26 19:16:05 tgl Exp $
 -->
 
 <chapter id="sql-syntax">
@@ -249,7 +249,7 @@ UPDATE "my_table" SET "a" = 5;
      <productname>PostgreSQL</productname> also allows single quotes
      to be escaped with a backslash (<literal>\'</literal>).  However,
      future versions of <productname>PostgreSQL</productname> will not
-     support this so applications using this should convert to the 
+     allow this, so applications using backslashes should convert to the 
      standard-compliant method outlined above.
     </para>
 
@@ -276,8 +276,8 @@ UPDATE "my_table" SET "a" = 5;
      eventually treat backslashes as literal characters to be
      standard-compliant. The proper way to specify escape processing is
      to use the escape string syntax to indicate that escape
-     processing is desired. Escape string syntax is specified by placing
-     the the letter <literal>E</literal> (upper or lower case) before
+     processing is desired. Escape string syntax is specified by writing
+     the letter <literal>E</literal> (upper or lower case) just before
      the string, e.g. <literal>E'\041'</>. This method will work in all
      future versions of <productname>PostgreSQL</productname>.
     </para>