Re: SI-read predicate locks on materialized views
Yugo Nagata <nagata@sraoss.co.jp>
From: Yugo NAGATA <nagata@sraoss.co.jp>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: Richard Guo <guofenglinux@gmail.com>, PostgreSQL-development
<pgsql-hackers@postgresql.org>
Date: 2022-09-30T01:12:13Z
Lists: 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>
Commits
-
Make materialized views participate in predicate locking
- 43351557d0d2 16.0 landed