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 | 029fa664ecb8687eb60633b4ccf230b457a1fb77 (patch) | |
| tree | 2147a55b8feefe7b7d5604ce26ea388abe2045fb /src/backend/executor/nodeBitmapOr.c | |
| parent | 139c439730b1444be88203cf867e60dd7533b294 (diff) | |
| download | postgresql-029fa664ecb8687eb60633b4ccf230b457a1fb77.tar.gz postgresql-029fa664ecb8687eb60633b4ccf230b457a1fb77.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/executor/nodeBitmapOr.c')
0 files changed, 0 insertions, 0 deletions