Re: BUG #15943: Valgrind-detected error in SlruPhysicalWritePage

Andres Freund <andres@anarazel.de> writes:
> Seems there's no reason to not zero initialize memory here? But perhaps just by initializing the stack variable?

I think all we need here is another suppression in
src/tools/valgrind.supp.  We have not insisted on zeroing
pad bytes that get sent to disk in the places already
enumerated in valgrind.supp, so why would we apply a
different rule to async.c?

            regards, tom lane