On 2/20/24 05:25, Zahir Lalani wrote:
-From: David G. Johnston
-Sent: Tuesday, February 20, 2024 1:20 PM
-To: Zahir Lalani
-Cc: Adrian Klaver ;
pgsql-general@lists.postgresql.org
-Subject: Re: Mat Views and Conflicts
-
-
-On Tuesday, February 20, 2024, Zahir Lalani <mailto:ZahirLal
On 2/20/24 04:20, Zahir Lalani wrote:
1) When you say '... ran the underlying query ...' are you referring to:
REFRESH MATERIALIZED VIEW
https://www.postgresql.org/docs/current/sql-refreshmaterializedview.html
2) What is the complete error message from the Postgres log?
Have I got it
-From: David G. Johnston
-Sent: Tuesday, February 20, 2024 1:20 PM
-To: Zahir Lalani
-Cc: Adrian Klaver ;
pgsql-general@lists.postgresql.org
-Subject: Re: Mat Views and Conflicts
-
-
-On Tuesday, February 20, 2024, Zahir Lalani <mailto:ZahirLalani@oliver.agency>
wrote:
-
-This su
On Tuesday, February 20, 2024, Zahir Lalani
wrote:
>
>
> This suggests that not all the MV data is cached and it still queries the
> source tables in some way?
>
>
No. That isn’t how MV work. If you include an MV relation in your query
from clause there is no reference or knowledge as to the
> -Original Message-
> From: Adrian Klaver
> Sent: Monday, February 19, 2024 7:36 PM
> To: Zahir Lalani ; pgsql-
> gene...@lists.postgresql.org
> Subject: Re: Mat Views and Conflicts
>
> On 2/19/24 09:52, Zahir Lalani wrote:
> > Hi All
> >
> > My
On 2/19/24 09:52, Zahir Lalani wrote:
Hi All
My understanding and hope was that Mat Views cache their data and that
is how they are so fast. But we are experience “cancelling statement due
to conflict with recovery” errors on MV’s with large data sets and I
thought that this could only
On Mon, Feb 19, 2024, 10:53 Zahir Lalani wrote:
> Hi All
>
>
>
> My understanding and hope was that Mat Views cache their data and that is
> how they are so fast. But we are experience “cancelling statement due to
> conflict with recovery” errors on MV’s with large data sets and I thought
> that
Hi All
My understanding and hope was that Mat Views cache their data and that is how
they are so fast. But we are experience "cancelling statement due to conflict
with recovery" errors on MV's with large data sets and I thought that this
could only happen if we ran the underlying query, not
