| From: | John Naylor <john(dot)naylor(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Revert "Change mbbisearch to return the character range" |
| Date: | 2021-08-26 14:07:43 |
| Message-ID: | E1mJG2h-0002BC-TK@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Revert "Change mbbisearch to return the character range"
This reverts commit 78ab944cd4b9977732becd9d0bc83223b88af9a2.
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.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/f8c8a8bccc23f6ca38f7a92c9a614e73fa1fcfb6
Modified Files
--------------
src/common/unicode/generate-unicode_width_table.pl | 4 +-
src/common/wchar.c | 21 +-
src/include/common/unicode_width_table.h | 386 ++++++++++-----------
3 files changed, 203 insertions(+), 208 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2021-08-26 15:06:00 | pgsql: Update display widths as part of updating Unicode |
| Previous Message | Amit Kapila | 2021-08-26 08:40:00 | Re: Separate out FileSet from SharedFileSet (was Re: pgsql: pgstat: Bring up pgstat in BaseInit() to fix uninitialized use o) |