aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-11-03 11:57:56 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2015-11-03 11:57:56 -0500
commitfc0b8935213cda555d2b3af2ed08da28ed120e31 (patch)
tree762b0a66964ac7450cffb3e547c6d1690baedba6 /doc/src
parenta69b0b2c14c614c129e89ae96d6f624375531760 (diff)
downloadpostgresql-fc0b8935213cda555d2b3af2ed08da28ed120e31.tar.gz
postgresql-fc0b8935213cda555d2b3af2ed08da28ed120e31.zip
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.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/func.sgml10
1 files changed, 0 insertions, 10 deletions
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 4d482ec91f0..60b9a090739 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4656,16 +4656,6 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
Non-capturing parentheses do not define subexpressions.
</para>
- <note>
- <para>
- Keep in mind that an escape's leading <literal>\</> will need to be
- doubled when entering the pattern as an SQL string constant. For example:
-<programlisting>
-'123' ~ E'^\\d{3}' <lineannotation>true</lineannotation>
-</programlisting>
- </para>
- </note>
-
<table id="posix-character-entry-escapes-table">
<title>Regular Expression Character-entry Escapes</title>