Re: Getting better results from valgrind leak tracking

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Getting better results from valgrind leak tracking
Date: 2021-03-29 21:18:11
Message-ID: CAApHDvr_BxaanDH4tUmW9yGsw33dhkwqDn8VO_pkMjnYg9uTUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 30 Mar 2021 at 06:38, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2021-03-29 11:48:47 +1300, David Rowley wrote:
> > I've done that in the attached. I added the
> > ParallelBlockTableScanWorkerData as a pointer field in
> > HeapScanDescData and change it so we only allocate memory for it for
> > just parallel scans. The field is left as NULL for non-parallel
> > scans.
>
> LGTM.

Thanks for having a look.

Pushed.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-03-29 21:21:39 Re: psql lacking clearerr()
Previous Message Alvaro Herrera 2021-03-29 21:05:46 Re: psql lacking clearerr()