From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 8 Jun 2009 14:57:21 +0000 (+0000)
Subject: Be a bit more verbose about the effects of string literal processing
X-Git-Url: http://waps.l3s.uni-hannover.de/gitweb/?a=commitdiff_plain;h=8378846fdffb329d33cb8b3732f56c5d9c92efc0;p=users%2Fsimon%2Fpostgres.git

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 0dd1c01cf7..f30e58b72a 100644
--- 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>