Re: Contention preventing locking
От
Konstantin Knizhnik
Тема
Re: Contention preventing locking
Дата
Msg-id
55146c68-0ded-a43b-68d1-b45e328f6cf6@postgrespro.ru
Ответ на
Re: Contention preventing locking (Simon Riggs)
Список
Дерево обсуждения
Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Amit Kapila <amit.kapila16@gmail.com>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Simon Riggs <simon@2ndquadrant.com>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Simon Riggs <simon@2ndquadrant.com>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Simon Riggs <simon@2ndquadrant.com>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Amit Kapila <amit.kapila16@gmail.com>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Amit Kapila <amit.kapila16@gmail.com>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Amit Kapila <amit.kapila16@gmail.com>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Contention preventing locking Amit Kapila <amit.kapila16@gmail.com>
Re: Contention preventing locking Michail Nikolaev <michail.nikolaev@gmail.com>
Re: Contention preventing locking Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
On 20.02.2018 14:26, Simon Riggs wrote: > Try locking the root tid rather than the TID, that is at least unique > per page for a chain of tuples, just harder to locate. > As far as I understand, it is necessary to traverse the whole page to locate root tuple, isn't it? If so, then I expect it to be too expensive operation. Scanning the whole page on tuple update seems to be not an acceptable solution. -- Konstantin Knizhnik Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
В списке pgsql-hackers по дате отправления
От: Matheus de Oliveira
Дата: