Be a bit more verbose about the effects of string literal processing

changes in plpgsql.  Per bug #4843.

diff --git a/doc/src/sgml/release-8.4.sgml b/doc/src/sgml/release-8.4.sgml
index 0dd1c01cf73a988192fc05fc349a0e1ff5e958fd..f30e58b72a852f10628c8fc42d8314793d24f21f 100644 (file)
--- a/doc/src/sgml/release-8.4.sgml
+++ b/doc/src/sgml/release-8.4.sgml
@@ -2303,6 +2303,14 @@
         Make processing of string literals and nested block comments
         match the main SQL parser's processing (Tom)
        </para>
+
+       <para>
+        In particular, the format string in <command>RAISE</> now works
+        the same as any other string literal, including being subject
+        to <varname>standard_conforming_strings</>.  This change also
+        fixes other cases in which valid commands would fail when
+        <varname>standard_conforming_strings</> is on.
+       </para>
       </listitem>
 
       <listitem>