| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Compile warnings in dbcommands.c building with meson |
| Date: | 2024-01-15 05:00:00 |
| Message-ID: | CACJufxFQxBwrSdT59DS2F2mT6oMg+J=rzxopxUjXoJV6U35LmQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi. one more feedback.
I tested the original repo setup, but it does not generate a warning
on my local setup.
meson setup --reconfigure ${BUILD} \
-Dprefix=${PG_PREFIX} \
-Dpgport=5463 \
-Dplpython=enabled \
-Dcassert=true \
-Dtap_tests=enabled \
-Dicu=enabled \
-Ddebug=true \
-Dnls=disabled
it generate warning, when I add -Dbuildtype=release :
meson setup --reconfigure ${BUILD} \
-Dprefix=${PG_PREFIX} \
-Dpgport=5463 \
-Dplpython=enabled \
-Dcassert=true \
-Dtap_tests=enabled \
-Dicu=enabled \
-Dbuildtype=release \
-Ddebug=true \
-Dnls=disabled
After applying the patch, the warning disappeared.
so it fixed the problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2024-01-15 05:19:56 | Re: the s_lock_stuck on perform_spin_delay |
| Previous Message | Michael Paquier | 2024-01-15 04:11:26 | Re: Test slots invalidations in 035_standby_logical_decoding.pl only if dead rows are removed |