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

Поиск
Список
Период
Сортировка
От Georgios
Тема Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Дата
Msg-id EY-r5luJpAHxpbphMAhaNWRMqYjODEcd91Zpa2RrcCzE8jgtyBwctmaXZgTz8KkP5XICls_HiWshFSiFss9alM7wXZs1CjXgimrc5z0t4lM=@protonmail.com
обсуждение исходный текст
Ответ на Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-hackers

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, July 21, 2020 11:52 PM, Peter Geoghegan <pg@bowt.ie> wrote:

> 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!

No worries at all. It happens and it was beneficial for me to read the patch.

//Georgios
>
>
----------------------------------------------------------------------------------------------------------------------
>
> Peter Geoghegan





В списке pgsql-hackers по дате отправления:

Предыдущее
От: torikoshia
Дата:
Сообщение: Re: Is it useful to record whether plans are generic or custom?
Следующее
От: David Rowley
Дата:
Сообщение: Re: Parallel Seq Scan vs kernel read ahead