Re: SI-read predicate locks on materialized views

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, 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-10-13 08:02:06
Message-ID: Y0fF/pd6FSU6Nk3m@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 30, 2022 at 10:12:13AM +0900, Yugo NAGATA wrote:
> Thank you for comment. Do you think it can be marked as Ready for Commiter?

Matviews have been discarded from needing predicate locks since
3bf3ab8 and their introduction, where there was no concurrent flavor
of refresh yet. Shouldn't this patch have at least an isolation test
to show the difference in terms of read-write conflicts with some
serializable transactions and REFRESH CONCURRENTLY?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2022-10-13 08:14:30 Re: ExecRTCheckPerms() and many prunable partitions
Previous Message Bharath Rupireddy 2022-10-13 07:58:02 Re: pg_receivewal fail to streams when the partial file to write is not fully initialized present in the wal receiver directory