Quick Links

Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)

From:	Daniel Gustafsson <daniel(at)yesql(dot)se>
To:	Peter Geoghegan <pg(at)bowt(dot)ie>
Cc:	Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject:	Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Date:	2020-07-02 14:48:37
Message-ID:	DAD9210C-A229-4B17-9F10-634A45832ED5@yesql.se
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

> On 26 Apr 2020, at 02:17, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:

> Attached is v2 of the patch series.

This patch fails to apply to HEAD due to conflicts in nbtpage.c, can you please
submit a rebased version?

cheers ./daniel

In response to

Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held) at 2020-04-26 00:17:17 from Peter Geoghegan

Responses

Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held) at 2020-07-02 17:11:53 from Peter Geoghegan

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Alvaro Herrera	2020-07-02 15:03:39	Re: Auxiliary Processes and MyAuxProc
Previous Message	Tom Lane	2020-07-02 14:46:17	Re: estimation problems for DISTINCT ON with FDW