diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-16 15:16:39 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-16 15:16:39 -0500 |
| commit | 89aa30a179686d86aeccddf715f039d1a15d2b30 (patch) | |
| tree | eb788a6e1a363c6c967d2bd87fc7d77bddbf534a /src/backend/parser/parse_expr.c | |
| parent | bea246117b402e59340c9efa0bdbdbe7c1ea8554 (diff) | |
| download | postgresql-89aa30a179686d86aeccddf715f039d1a15d2b30.tar.gz postgresql-89aa30a179686d86aeccddf715f039d1a15d2b30.zip | |
Use "true" not "TRUE" in one ICU function call.
This was evidently missed in commit 6337865f3, which generally did
s/TRUE/true/ everywhere. It escaped notice up to now because ICU
versions before ICU 68 provided definitions of "TRUE" and "FALSE"
regardless. With ICU 68, it fails to compile.
Per report from Condor. Back-patch to v11 where 6337865f3 came in.
(I've not tested v10, where this call originated, but I imagine
it's fine since we defined TRUE in c.h back then.)
Discussion: https://postgr.es/m/7a6f3336165bfe3ca66abcda7966f9d0@stz-bg.com
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions