Postgres Pro
Downloads
Home   >   mailing lists

Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Date
Msg-id CAH2-WzmgC28b7qO4PsjB990xt3qg=RgtFXXFDavN7dHm3kMB_A@mail.gmail.com
Whole thread Raw
In response to Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Georgios Kokolatos <gkokolatos@protonmail.com>)
Responses Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Georgios <gkokolatos@protonmail.com>)
List pgsql-hackers
Tree view 
On Mon, Jul 6, 2020 at 1:35 AM Georgios Kokolatos
<gkokolatos@protonmail.com> wrote:
> As a general overview, the series of patches in the mail thread do match their description. The addition of the
stricter,explicit use of instrumentation does improve the design as the distinction of the use cases requiring a pin or
alock is made more clear. The added commentary is descriptive and appears grammatically correct, at least to a non
nativespeaker. 

I didn't see this review until now because it ended up in gmail's spam
folder. :-(

Thanks for taking a look at it!

--
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Which SET TYPE don't actually require a rewrite
Next
From: Tom Lane
Date:
Subject: Re: Infinities in type numeric