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:30 -0400 |
| commit | e2e46a9d1c22aa8a6ef7fd498a063fc7d4d300ef (patch) | |
| tree | 2211b8e1b814af9cf783bb81bf25ea7f44710738 /src/backend/regex/regexec.c | |
| parent | 541ec18acf2f6c8df095e45af980f59b82475d1e (diff) | |
| download | postgresql-e2e46a9d1c22aa8a6ef7fd498a063fc7d4d300ef.tar.gz postgresql-e2e46a9d1c22aa8a6ef7fd498a063fc7d4d300ef.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