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

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Дата
Msg-id CAH2-WzmF0ECfd04uy6ONBBE6RYfTXB3=wxzO36C4rKrWygvKsQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения 
On Sat, Jul 18, 2020 at 7:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wonder whether skink's failure today is due to this change:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2020-07-18%2018%3A01%3A10

That seems extremely likely. I think that I need to do something like
what you see in the attached.

Anyway, I'll take care of it tomorrow. Sorry for missing it before my commit.

-- 
Peter Geoghegan
Вложения

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Следующее
От: Andy Fan
Дата:
Сообщение: Re: [PATCH] Keeps tracking the uniqueness with UniqueKey