From: | Akshaya Acharya <akshaya(dot)acharya(dot)01(at)gmail(dot)com> |
---|---|
To: | bbxiao1(at)gmail(dot)com |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Refresh materialized view deadlocking? |
Date: | 2018-07-10 17:58:36 |
Message-ID: | CABPa3Q515JKSn028S_GoyuRrnZF335umbcMDtSVbQNAcy2nv3w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Xiao
From
https://www.postgresql.org/docs/current/static/sql-refreshmaterializedview.html
For concurrently option
" Even with this option only one REFRESH at a time may run against any one
materialized view. "
I would guess yes.
Regards, Akshaya
On Tue, 10 Jul 2018 at 23:24, Xiao Ba <bbxiao1(at)gmail(dot)com> wrote:
> I have a materialized view that gets refreshed concurrently every 10
> seconds (b/c it contains time sensitive stuff). At times it appears to get
> backed up so there are multiple refreshes queued and then gets stuck
> waiting for a lock? Does anybody know if this is expected behavior? Am I
> supposed to be manually managing to ensure that only one refresh is being
> requested at a time?
>
> Thanks,
> Xiao
>
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Hemmer | 2018-07-10 18:37:57 | max_standby_streaming_delay not enforced |
Previous Message | Xiao Ba | 2018-07-10 17:53:07 | Refresh materialized view deadlocking? |