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 cca2d033b2c8f773762f2f96164cdf069fdf85d5..b00cb16dba7a2c02142bcb15284f84eb49ffdfca 100644 (file)
--- a/doc/src/sgml/release-8.4.sgml
+++ b/doc/src/sgml/release-8.4.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  
@@ -2303,6 +2303,14 @@
         Make processing of string literals and nested block comments
         match the main SQL parser's processing (Tom)
        
+
+       
+        In particular, the format string in RAISE now works
+        the same as any other string literal, including being subject
+        to standard_conforming_strings.  This change also
+        fixes other cases in which valid commands would fail when
+        standard_conforming_strings is on.
+