Re: SI-read predicate locks on materialized views
От | Yugo NAGATA |
---|---|
Тема | Re: SI-read predicate locks on materialized views |
Дата | |
Msg-id | 20220930101213.7fdc3d08329ea01f23eca97f@sraoss.co.jp обсуждение исходный текст |
Ответ на | Re: SI-read predicate locks on materialized views (Dilip Kumar <dilipbalaut@gmail.com>) |
Ответы |
Re: SI-read predicate locks on materialized views
|
Список | 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 по дате отправления: