diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-11-03 11:57:56 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-11-03 11:58:03 -0500 |
| commit | fdae4a93e9df6b9b0f0ef5b0ccff697e4859710f (patch) | |
| tree | b298ce004fd650e5aad40537f8ee558531279730 | |
| parent | f4057cdffc355f5d4a9d8411fb953069be6d72ea (diff) | |
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.
| -rw-r--r-- | doc/src/sgml/func.sgml | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 290ba52e7ec..ecca7922ace 100644 --- 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. </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> |