diff options
| author | John Naylor <john.naylor@postgresql.org> | 2021-08-26 10:06:12 -0400 |
|---|---|---|
| committer | John Naylor <john.naylor@postgresql.org> | 2021-08-26 10:06:12 -0400 |
| commit | 1563ecbc1be8b8e5c57651cf5c87f90dea9aea8f (patch) | |
| tree | 352dc9c770ec3e66279b7cd6b26c08097e08c0e3 /src/backend/regex/regexec.c | |
| parent | f8c8a8bccc23f6ca38f7a92c9a614e73fa1fcfb6 (diff) | |
| download | postgresql-1563ecbc1be8b8e5c57651cf5c87f90dea9aea8f.tar.gz postgresql-1563ecbc1be8b8e5c57651cf5c87f90dea9aea8f.zip | |
Revert "Rename unicode_combining_table to unicode_width_table"
This reverts commit eb0d0d2c7300c9c5c22b35975c11265aa4becc84.
After I had committed eb0d0d2c7 and 78ab944cd, I decided to add
a sanity check for a "can't happen" scenario just to be cautious.
It turned out that it already happened in the official Unicode source
data, namely that a character can be both wide and a combining
character. This fact renders the aforementioned commits unnecessary,
so revert both of them.
Discussion: https://www.postgresql.org/message-id/CAFBsxsH5ejH4-1xaTLpSK8vWoK1m6fA1JBtTM6jmBsLfmDki1g%40mail.gmail.com
Diffstat (limited to 'src/backend/regex/regexec.c')
0 files changed, 0 insertions, 0 deletions