On Thu, Jan 25, 2018 at 10:39 AM, Robert Haas <robertmh...@gmail.com> wrote: > On Mon, Jan 22, 2018 at 9:46 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> Robert Haas <robertmh...@gmail.com> writes: >>> Tom, do you want to double-check that this fixes it for you? >> >> I can confirm that a valgrind run succeeded for me with the patch >> in place. > > Committed. Sorry for the delay.
FYI I'm planning to look into adding a valgrind check to the commitfest CI thing I run so we can catch these earlier without committer involvement. It's super slow because of all those pesky regression tests so I'll probably need to improve the scheduling logic a bit to make it useful first (prioritising new patches or something, since otherwise it'll take up to multiple days to get around to valgrind-testing any given patch...). -- Thomas Munro http://www.enterprisedb.com
