Message-ID: <4ba1d48f-c946-404b-9919-231bcbee0130@gmail.com>
Date: Sat, 6 Jul 2024 11:09:23 +0530
MIME-Version: 1.0
User-Agent: Betterbird (Linux)
Subject: Re: confused about material view locks please explain
To: pgsql-general@lists.postgresql.org
References: <3eed1916-a166-42b7-862e-692887336652@gmail.com>
 <20240705154035.qjoey3eaqaqitthn@hjp.at>
Content-Language: en-US
From: Krishnakant Mane <kkproghub@gmail.com>
In-Reply-To: <20240705154035.qjoey3eaqaqitthn@hjp.at>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/4ba1d48f-c946-404b-9919-231bcbee0130%40gmail.com>
Precedence: bulk


On 7/5/24 21:10, Peter J. Holzer wrote:
> If I understand https://github.com/sraoss/pg_ivm correctly, the
> materialized view will be updated within the same transaction. So it's
> just the same as any other change in the database:
>
> Neither client will wait for the other. The first client will see either
> the old or the new state depending on whether the second client manages
> to commit soon enough.

Thank you Peter.

So does that mean both the processes work concurrently?

  I had understood that while an update is happening to an IVM (material 
view ) the view is locked till the update is complete.

If so then how would both the clients have simultaneous access?


Regards.


>          

>