diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-05-10 23:44:33 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-05-10 23:44:33 -0400 |
commit | ea964a451e51a32b71d004d261874adb1e135066 (patch) | |
tree | 34904c0a331476f3daaa2632dd067a853f414c6a | |
parent | 64cc297dc9875a6feb3a310038707b6119b775ca (diff) | |
download | postgresql-ea964a451e51a32b71d004d261874adb1e135066.tar.gz postgresql-ea964a451e51a32b71d004d261874adb1e135066.zip |
Be more explicit about the meaning of the change in standard_conforming_strings.
-rw-r--r-- | doc/src/sgml/release-9.1.sgml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml index 7737381e798..280e0bb1424 100644 --- a/doc/src/sgml/release-9.1.sgml +++ b/doc/src/sgml/release-9.1.sgml @@ -58,8 +58,9 @@ </para> <para> - This removes a long-standing incompatibility with the SQL - standard; <link + By default, backslashes are now ordinary characters in string literals, + not escape characters. This change removes a long-standing + incompatibility with the SQL standard. <link linkend="guc-escape-string-warning"><varname>escape_string_warning</></link> has produced warnings about this usage for years. <literal>E''</> strings are the proper way to embed backslash escapes in strings and are |