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-20 16:10:12 |
Message-ID: | b79d1e63-b770-4d8d-984b-77fc3d9c84e7@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 wrong??
>>>
>>> Z
>>>
>>
>> --
>> Adrian Klaver
>> adrian(dot)klaver(at)aklaver(dot)com
>
> To clarify:
>
> We are not running the REFRESH. We are only running the materialised view. We used to run the non-view query directly and always suffered from the conflict with recovery error due to data changes on the replica server during the query run. We increased the max_standby_streaming_delay quite a lot, but these are very heavy queries which take a long time. So that is when we decided to convert to an MV. We get the conflict a lot less, but still enough to be annoying. This suggests that not all the MV data is cached and it still queries the source tables in some way?
2) What is the complete error message from the Postgres log?
>
> Z
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-02-20 16:13:21 | Re: Mat Views and Conflicts |
Previous Message | Greg Sabino Mullane | 2024-02-20 14:50:02 | Re: User pooler error: unsupported startup parameter: extra_float_digits |