aboutsummaryrefslogtreecommitdiff
path: root/src/common/wchar.c
diff options
context:
space:
mode:
authorJohn Naylor <john.naylor@postgresql.org>2021-08-26 10:06:12 -0400
committerJohn Naylor <john.naylor@postgresql.org>2021-08-26 10:06:12 -0400
commit1563ecbc1be8b8e5c57651cf5c87f90dea9aea8f (patch)
tree352dc9c770ec3e66279b7cd6b26c08097e08c0e3 /src/common/wchar.c
parentf8c8a8bccc23f6ca38f7a92c9a614e73fa1fcfb6 (diff)
downloadpostgresql-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/common/wchar.c')
-rw-r--r--src/common/wchar.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/common/wchar.c b/src/common/wchar.c
index bb97b5f54f4..0636b8765ba 100644
--- a/src/common/wchar.c
+++ b/src/common/wchar.c
@@ -644,7 +644,7 @@ mbbisearch(pg_wchar ucs, const struct mbinterval *table, int max)
static int
ucs_wcwidth(pg_wchar ucs)
{
-#include "common/unicode_width_table.h"
+#include "common/unicode_combining_table.h"
/* test for 8-bit control characters */
if (ucs == 0)