Re: SKIP LOCKED DATA (work in progress)

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: SKIP LOCKED DATA (work in progress)
Дата
Msg-id CADLWmXWxuTLwRwXSiXzdeXyxXzTiC532pFUmVs8OuLp6XPE5Mw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: SKIP LOCKED DATA (work in progress)  (Thomas Munro <munro@ip9.org>)
Ответы Re: SKIP LOCKED DATA (work in progress)  (David Rowley <dgrowleyml@gmail.com>)
Re: SKIP LOCKED DATA (work in progress)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
On 27 July 2014 23:19, Thomas Munro <munro@ip9.org> wrote:
> On the subject of isolation tests, I think skip-locked.spec is only
> producing schedules that reach third of the three 'return
> HeapTupleWouldBlock' statements in heap_lock_tuple.  I will follow up
> with some more thorough isolation tests in the next week or so to
> cover the other two, and some other scenarios and interactions with
> other feature.

Now with extra isolation tests so that the three different code
branches that can skip rows are covered.  I temporarily added some
logging lines to double check that the expected branches are reached
by each permutation while developing the specs.  They change the
output and are not part of the patch -- attaching separately.

Вложения

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Making joins involving ctid work for the benefit of UPSERT
Следующее
От: Andres Freund
Дата:
Сообщение: Re: [RFC] Should smgrtruncate() avoid sending sinval message for temp relations