Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)
Alexander Korotkov <a.korotkov@postgrespro.ru>
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Teodor Sigaev <teodor@sigaev.ru>
Cc: Dmitry Ivanov <d.ivanov@postgrespro.ru>,
Shubham Barai <shubhambaraiss@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>,
Andrey Borodin <x4mmm@yandex-team.ru>, Thomas Munro <thomas.munro@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>,
Andrew Borodin <amborodin86@gmail.com>, Kevin Grittner <kgrittn@gmail.com>
Date: 2018-03-29T13:10:24Z
Lists: pgsql-hackers
Attachments
- Predicate-Locking-in-gin-index_v11.patch (application/octet-stream) patch v11
On Thu, Mar 29, 2018 at 1:38 PM, Teodor Sigaev <teodor@sigaev.ru> wrote: > The next question what I see: why do not we lock entry leaf pages in some >> cases? >> > > I've modified patch to predicate lock each leaf (entry or posting) page. > Now patch reaches commitable state from my point view. I made some enhancements in comments and readme. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Commits
-
Re-think predicate locking on GIN indexes.
- 0bef1c0678d9 11.0 landed
-
Predicate locking in GIN index
- 43d1ed60fdd9 11.0 landed