Re: SI-read predicate locks on materialized views - Mailing list pgsql-hackers

From Yugo NAGATA
Subject Re: SI-read predicate locks on materialized views
Date
Msg-id 20220930101213.7fdc3d08329ea01f23eca97f@sraoss.co.jp
Whole thread Raw
In response to Re: SI-read predicate locks on materialized views  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: SI-read predicate locks on materialized views
List pgsql-hackers
On Fri, 9 Sep 2022 16:27:45 +0530
Dilip Kumar <dilipbalaut@gmail.com> wrote:

> On Tue, Jul 26, 2022 at 3:31 PM Richard Guo <guofenglinux@gmail.com> wrote:
> >
> >
> > On Tue, Jul 26, 2022 at 3:44 PM Yugo NAGATA <nagata@sraoss.co.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.

Thank you for comment. Do you think it can be marked as Ready for Commiter?

Regards,
Yugo Nagata

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


-- 
Yugo NAGATA <nagata@sraoss.co.jp>



pgsql-hackers by date:

Previous
From: Yugo NAGATA
Date:
Subject: Re: pgbench: using prepared BEGIN statement in a pipeline could cause an error
Next
From: Thomas Munro
Date:
Subject: Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes?