pgsql: Fix documentation of regular expression character-entry escapes.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix documentation of regular expression character-entry escapes.
Date: 2015-09-16 18:51:22
Message-ID: E1ZcHne-0000wy-AF@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix documentation of regular expression character-entry escapes.

The docs claimed that \uhhhh would be interpreted as a Unicode value
regardless of the database encoding, but it's never been implemented
that way: \uhhhh and \xhhhh actually mean exactly the same thing, namely
the character that pg_mb2wchar translates to 0xhhhh. Moreover we were
falsely dismissive of the usefulness of Unicode code points above FFFF.
Fix that.

It's been like this for ages, so back-patch to all supported branches.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/dad7ea7e4dcc9ebdfb5480aa91cd1424135214e9

Modified Files
--------------
doc/src/sgml/func.sgml | 21 +++++++++++++++++----
1 file changed, 17 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-09-16 19:25:32 pgsql: Sync regex code with Tcl 8.6.4.
Previous Message Tom Lane 2015-09-16 16:09:16 pgsql: Don't use "#" as an abbreviation for "number" in PL/Tcl error me