| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Zahir Lalani <ZahirLalani(at)oliver(dot)agency> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Mat Views and Conflicts |
| Date: | 2024-02-19 18:13:12 |
| Message-ID: | CAKFQuwaQ+1sCCVfy82b9TPzvh64Z30xa2mxc9yfYcjYFaqyUUA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Feb 19, 2024, 10:53 Zahir Lalani <ZahirLalani(at)oliver(dot)agency> 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 happen if we ran the underlying query, not the Mat
> View?
>
>
>
>
>
> Have I got it wrong??
>
A materialized view is, physically, just like any other table. It is a
cache but only in the sense that tables cache real life data.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-02-19 19:36:12 | Re: Mat Views and Conflicts |
| Previous Message | Zahir Lalani | 2024-02-19 17:52:53 | Mat Views and Conflicts |