diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 22d4f615259..91a9379ae77 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4669,7 +4669,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
\e>
the character whose collating-sequence name
is ESC>,
- or failing that, the character with octal value 033
+ or failing that, the character with octal value 033>
@@ -4695,15 +4695,17 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
\u>wxyz>
(where wxyz> is exactly four hexadecimal digits)
- the UTF16 (Unicode, 16-bit) character U+>wxyz>
- in the local byte ordering
+ the character whose hexadecimal value is
+ 0x>wxyz>
+
\U>stuvwxyz>
(where stuvwxyz> is exactly eight hexadecimal
digits)
- reserved for a hypothetical Unicode extension to 32 bits
+ the character whose hexadecimal value is
+ 0x>stuvwxyz>
@@ -4752,6 +4754,17 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
Octal digits are 0>-7>.
+
+ Numeric character-entry escapes specifying values outside the ASCII range
+ (0-127) have meanings dependent on the database encoding. When the
+ encoding is UTF-8, escape values are equivalent to Unicode code points,
+ for example \u1234> means the character U+1234>.
+ For other multibyte encodings, character-entry escapes usually just
+ specify the concatenation of the byte values for the character. If the
+ escape value does not correspond to any legal character in the database
+ encoding, no error will be raised, but it will never match any data.
+
+
The character-entry escapes are always taken as ordinary characters.
For example, \135> is ]> in ASCII, but