On Sat, 6 Dec 2025 at 21:40, Tom Lane <[email protected]> wrote: > Yeah. However, selecting different PG_PRINTF_ATTRIBUTE values for > C and C++ mode seems to get the job done. I've confirmed the attached > silences these warnings for me when mixing-and-matching gcc and clang.
I've definitely run into this myself a bunch of times. I'm wondering if we should do this for more of these compiler features, e.g. HAVE_TYPEOF is strictly wrong for C++ builds afaict[1]. [1]: https://www.postgresql.org/message-id/flat/cageczqr21onnkizo_1rlwo0-16kg1jbxnvq-wymyw0-_1cu...@mail.gmail.com
