Change HAVE_LIBLZ4 and HAVE_LIBZSTD tests to USE_LZ4 and USE_ZSTD.
authorRobert Haas <rhaas@postgresql.org>
Tue, 15 Mar 2022 17:06:25 +0000 (13:06 -0400)
committerRobert Haas <rhaas@postgresql.org>
Tue, 15 Mar 2022 17:06:25 +0000 (13:06 -0400)
commit75eae090876f4d47bf6a1e1016627b75da612307
tree55bd88228194696d5c1c6e25b2332a17148c978c
parent695f459f1713303ba33b76eeb866c6501dff6380
Change HAVE_LIBLZ4 and HAVE_LIBZSTD tests to USE_LZ4 and USE_ZSTD.

These tests were added recently, but older code tests USE_LZ4 rathr
than HAVE_LIBLZ4, so let's follow the established precedent. It
also seems more consistent with the intent of the configure tests,
since I think that the USE_* symbols are intended to correspond to
what the user requested, and the HAVE_* symbols to what configure
found while probing.

Discussion: http://postgr.es/m/CA+Tgmoap+hTD2-QNPJLH4tffeFE8MX5+xkbFKMU3FKBy=ZSNKA@mail.gmail.com
src/backend/replication/basebackup_lz4.c
src/backend/replication/basebackup_zstd.c
src/bin/pg_basebackup/bbstreamer_lz4.c
src/bin/pg_basebackup/bbstreamer_zstd.c
src/bin/pg_basebackup/pg_receivewal.c
src/bin/pg_basebackup/t/020_pg_receivewal.pl
src/bin/pg_basebackup/walmethods.c
src/bin/pg_dump/t/002_pg_dump.pl
src/bin/pg_verifybackup/t/008_untar.pl
src/bin/pg_verifybackup/t/009_extract.pl
src/bin/pg_verifybackup/t/010_client_untar.pl