Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Dmitry Ivanov <d(dot)ivanov(at)postgrespro(dot)ru>, Shubham Barai <shubhambaraiss(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Borodin <amborodin86(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>
Subject: Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)
Date: 2018-03-29 13:10:24
Message-ID: CAPpHfdsdZSdzC0uWk_jAGT0BVMX9M77hOxKcXksDZMkUUXnVBQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers pgsql-www

On Thu, Mar 29, 2018 at 1:38 PM, Teodor Sigaev <teodor(at)sigaev(dot)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

Attachment Content-Type Size
Predicate-Locking-in-gin-index_v11.patch application/octet-stream 49.8 KB

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Teodor Sigaev 2018-03-29 17:07:33 Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)
Previous Message Alvaro Herrera 2018-03-29 12:06:26 Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2018-03-29 13:15:10 Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Previous Message David Rowley 2018-03-29 13:09:33 Re: Parallel Aggregates for string_agg and array_agg