| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Zahir Lalani <ZahirLalani(at)oliver(dot)agency>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Mat Views and Conflicts |
| Date: | 2024-02-19 19:36:12 |
| Message-ID: | c02bdeda-9ffb-42a5-8b6d-c13b9380f0fe@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 happen if we ran the underlying query, not
> the Mat View?
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 wrong??
>
> Z
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-02-19 19:45:13 | Re: DETAIL: Could not open file "pg_xact/0EEA": No such file or directory |
| Previous Message | David G. Johnston | 2024-02-19 18:13:12 | Re: Mat Views and Conflicts |