On 3/28/18 04:06, Fabien COELHO wrote: > Would the project feel appropriate to: > > - fix these warnings (other than putting -Wno-format-truncation or > similar workarounds...).
I've been tracking gcc-8, and I have a patch ready, but these things change a bit with every compiler snapshot, so I'm waiting until things settle down. > - add permanent gcc/clang trunk beasts with -Werror > (if so, I'd suggest cannonball & seanettle for the names). I would not like that. The build farm success should ideally be a function of correct PostgreSQL code, not external factors. If an in-progress compiler does funny things, what are we supposed to do about that? Generally, fixing up PostgreSQL for a new compiler release isn't a major effort and can be done briefly before the release of the compiler. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
