diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-09-16 14:50:12 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-09-16 14:50:23 -0400 |
| commit | d97bdb082690980a78ca6e2bbe0c6d863caef32f (patch) | |
| tree | 2f16641f3ba4a73c4eadaf98888463e863e09eae /src/backend/regex/regexec.c | |
| parent | 3047a9b9ef0db126c7f40acde51f78a1bbaa6dd6 (diff) | |
| download | postgresql-d97bdb082690980a78ca6e2bbe0c6d863caef32f.tar.gz postgresql-d97bdb082690980a78ca6e2bbe0c6d863caef32f.zip | |
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.
Diffstat (limited to 'src/backend/regex/regexec.c')
0 files changed, 0 insertions, 0 deletions