Re: confused about material view locks please explain

From: Krishnakant Mane <kkproghub(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: confused about material view locks please explain
Date: 2024-07-06 05:39:23
Message-ID: 4ba1d48f-c946-404b-9919-231bcbee0130@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


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.

>

>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2024-07-06 05:39:38 Re: Can a long running procedure detect when smart shutdown is pending?
Previous Message Dennis White 2024-07-05 23:36:07 Re: Can a long running procedure detect when smart shutdown is pending?