aboutsummaryrefslogtreecommitdiff
path: root/src/backend/storage/file/fd.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-11-16 15:16:39 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2020-11-16 15:16:39 -0500
commit53c7b4f6221be2800ba49840ce29cb1b5c0b1ab7 (patch)
tree371a31d1bc85e6898983e3455e149b6bfc21c566 /src/backend/storage/file/fd.c
parentb7fc2593233f5bd1e651852c6d7780cef561a797 (diff)
downloadpostgresql-53c7b4f6221be2800ba49840ce29cb1b5c0b1ab7.tar.gz
postgresql-53c7b4f6221be2800ba49840ce29cb1b5c0b1ab7.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/storage/file/fd.c')
0 files changed, 0 insertions, 0 deletions