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

Поиск
Список
Период
Сортировка
От Georgios Kokolatos
Тема Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Дата
Msg-id 159402449672.1150.17670816824105739624.pgcf@coridan.postgresql.org
обсуждение исходный текст
Ответ на Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-hackers
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.
 

Unfortunately though, the two bug fixes do not seem to apply.

Also, there is a small issue regarding the process, not the content of the patches. In CF app there is a latest
attachment (v3-0002-Add-nbtree-Valgrind-buffer-lock-checks.patch)  which does not appear in the mail thread.  Before
changingthe status, I will kindly ask for the complete latest series that applies in the mail thread. 

The new status of this patch is: Waiting on Author

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

Предыдущее
От: "kato-sho@fujitsu.com"
Дата:
Сообщение: Performing partition pruning using row value
Следующее
От: "Andrey V. Lepikhov"
Дата:
Сообщение: Re: Asymmetric partition-wise JOIN