diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-09-22 11:00:58 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-09-22 11:00:58 -0400 |
| commit | 85feb77aa09cda9ff3e12cf95c757c499dc25343 (patch) | |
| tree | 313b8bb0eb9cf4cff63a92dd5345d9d5c51b3b3a /src/backend/access/gist/gistproc.c | |
| parent | e6023ee7fa73a2d9a2d7524f63584844b2291def (diff) | |
| download | postgresql-85feb77aa09cda9ff3e12cf95c757c499dc25343.tar.gz postgresql-85feb77aa09cda9ff3e12cf95c757c499dc25343.zip | |
Assume wcstombs(), towlower(), and sibling functions are always present.
These functions are required by SUS v2, which is our minimum baseline
for Unix platforms, and are present on all interesting Windows versions
as well. Even our oldest buildfarm members have them. Thus, we were not
testing the "!USE_WIDE_UPPER_LOWER" code paths, which explains why the bug
fixed in commit e6023ee7f escaped detection. Per discussion, there seems
to be no more real-world value in maintaining this option. Hence, remove
the configure-time tests for wcstombs() and towlower(), remove the
USE_WIDE_UPPER_LOWER symbol, and remove all the !USE_WIDE_UPPER_LOWER code.
There's not actually all that much of the latter, but simplifying the #if
nests is a win in itself.
Discussion: https://postgr.es/m/20170921052928.GA188913@rfd.leadboat.com
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions