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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org>
Subject: Re: BUG #15943: Valgrind-detected error in SlruPhysicalWritePage
Date: 2019-08-08 16:43:32
Message-ID: 20190808164332.GA20632@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2019-08-08 18:21:04 Re: BUG #15943: Valgrind-detected error in SlruPhysicalWritePage
Previous Message Andrew Zimmerman 2019-08-08 16:30:00 Error in COPY command with files over 1GB