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

From: Shubham Barai <shubhambaraiss(at)gmail(dot)com>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: 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-16 12:10:54
Message-ID: CALxAEPs9cNsjGCqkKM0CTpMExOSViRMBcWZQdquXA-iPqoxutA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers pgsql-www

On 16 March 2018 at 03:57, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
wrote:

> On Tue, Mar 13, 2018 at 3:25 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
> wrote:
>
>> Alexander Korotkov wrote:
>>
>> > And what happen if somebody concurrently set (fastupdate = on)?
>> > Can we miss conflicts because of that?
>>
>> I think it'd be better to have that option require AccessExclusive lock,
>> so that it can never be changed concurrently with readers. Seems to me
>> that penalizing every single read to cope with this case would be a bad
>> trade-off.
>
>
> As Andrey Borodin mentioned, we already do. Sorry for buzz :)
>
>
>
I have updated the patch based on suggestions.

Regards,
Shubham

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

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Jonathan S. Katz 2018-03-16 13:10:47 Re: Updating our entry on the professional services page
Previous Message Daniel Gustafsson 2018-03-16 11:34:43 Re: Updating our entry on the professional services page

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-03-16 12:15:54 Re: pg_get_functiondef forgets about most GUC_LIST_INPUT GUCs
Previous Message Pavan Deolasee 2018-03-16 11:59:36 Re: ON CONFLICT DO UPDATE for partitioned tables