Remove obsolete advice about doubling backslashes in regex escapes.

Standard-conforming literals have been the default for long enough that
it no longer seems necessary to go out of our way to tell people to write
regex escapes illegibly.

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 290ba52e7ec1d9427fd8b9f5729cadca1a4ccb8f..ecca7922acec3cbb73277313afb0b770e65bcc78 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4642,16 +4642,6 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
     Non-capturing parentheses do not define subexpressions.
    
 
-   
-    
-     Keep in mind that an escape's leading \ will need to be
-     doubled when entering the pattern as an SQL string constant.  For example:
-
-'123' ~ E'^\\d{3}' true
-
-    
-   
-
    
     Regular Expression Character-entry Escapes