Andres Freund <and...@anarazel.de> writes: > I wonder if we should instead either ask those buildfarm animals to be > disabled or have the warning manually disabled. I don't think it's a good > investment on our part to work towards warning cleanliness on clang 4 and 5, > on distros from 2017 and and 2018 respectively.
Well, if we don't want to fix it I can just adjust my warning-scraping script to ignore these. Let's wait a bit and see if any newer compilers warn similarly before deciding. regards, tom lane