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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-21 22:53:07
Message-ID: CAH2-WznX4dpvdhuqwGjCZwVzt1oBSaF0-tt6vsfS1jQLcbJ8iw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 17, 2020 at 5:53 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Pushed the first patch just now, and intend to push the other one soon. Thanks!

Pushed the second piece of this (the nbtree patch) just now.

Thanks for the review!
--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2020-07-21 23:35:55 Re: Index Skip Scan (new UniqueKeys)
Previous Message Tom Lane 2020-07-21 22:25:00 Re: v13 planner ERROR: could not determine which collation to use for string comparison