Re: BUG #15943: Valgrind-detected error in SlruPhysicalWritePage - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #15943: Valgrind-detected error in SlruPhysicalWritePage
Date
Msg-id 20190808164332.GA20632@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #15943: Valgrind-detected error in SlruPhysicalWritePage  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: BUG #15943: Valgrind-detected error in SlruPhysicalWritePage  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
On 2019-Aug-08, Alexander Lakhin wrote:

> Indeed, "memset(&qe, 0, sizeof(qe));" added in the beginning of
> asyncQueueAddEntries fixes the issue.
> More interestingly, "memset(qe.data, 0, sizeof(qe.data));" in the same
> place fixes it too (the patch is attached).

Maybe VALGRIND_MAKE_MEM_DEFINED?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: Andrew Zimmerman
Date:
Subject: Error in COPY command with files over 1GB
Next
From: Andres Freund
Date:
Subject: Re: BUG #15943: Valgrind-detected error in SlruPhysicalWritePage