| From: | Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SI-read predicate locks on materialized views |
| Date: | 2022-09-30 01:12:13 |
| Message-ID: | 20220930101213.7fdc3d08329ea01f23eca97f@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 9 Sep 2022 16:27:45 +0530
Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> 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.
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(at)sraoss(dot)co(dot)jp>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2022-09-30 01:15:30 | Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes? |
| Previous Message | Yugo NAGATA | 2022-09-30 01:07:43 | Re: pgbench: using prepared BEGIN statement in a pipeline could cause an error |