Re: SI-read predicate locks on materialized views

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SI-read predicate locks on materialized views
Date: 2022-09-09 10:57:45
Message-ID: CAFiTN-s1MnSGJFVUcC56SOdh1juC8NtfCLVA7vS-Yi9uuQ=b6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 26, 2022 at 3:31 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
>
>
> On Tue, Jul 26, 2022 at 3:44 PM Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> wrote:
>>
>> If such two transactions run concurrently, a write skew anomaly occurs,
>> and the result of order_summary refreshed in T1 will not contain the
>> record inserted in T2.

Yes we do have write skew anomaly. I think the patch looks fine to me.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo NAGATA 2022-09-09 11:10:32 Re: Implementing Incremental View Maintenance
Previous Message Alvaro Herrera 2022-09-09 10:31:49 Re: [BUG] wrong FK constraint name when colliding name on ATTACH