aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2022-12-29 12:47:29 -0800
committerAndres Freund <andres@anarazel.de>2023-01-02 15:49:33 -0800
commitc6e75e4c2703d8eb7cb14cbf94a3d3dc36fdabbd (patch)
treec7d0b6e19e90c51afc3484fe7ecafee35cb8e47b /src/backend/executor/nodeModifyTable.c
parentfbed54fb3890894055072381bb13850baf524ba5 (diff)
downloadpostgresql-c6e75e4c2703d8eb7cb14cbf94a3d3dc36fdabbd.tar.gz
postgresql-c6e75e4c2703d8eb7cb14cbf94a3d3dc36fdabbd.zip
perl: Hide warnings inside perl.h when using gcc compatible compiler
New versions of perl trigger warnings within perl.h with our compiler flags. At least -Wdeclaration-after-statement, -Wshadow=compatible-local are known to be problematic. To avoid these warnings, conditionally use #pragma GCC system_header before including plperl.h. Alternatively, we could add the include paths for problematic headers with -isystem, but that is a larger hammer and is harder to search for. A more granular alternative would be to use #pragma GCC diagnostic push/ignored/pop, but gcc warns about unknown warnings being ignored, so every to-be-ignored-temporarily compiler warning would require its own pg_config.h symbol and #ifdef. As the warnings are voluminous, it makes sense to backpatch this change. But don't do so yet, we first want gather buildfarm coverage - it's e.g. possible that some compiler claiming to be gcc compatible has issues with the pragma. Author: Andres Freund <andres@anarazel.de> Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: Discussion: https://postgr.es/m/20221228182455.hfdwd22zztvkojy2@awork3.anarazel.de
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions