| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | ext-adarsh(dot)kumar(at)elisa(dot)fi, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17714: Refresh materialized view does not update all date |
| Date: | 2022-12-12 17:03:23 |
| Message-ID: | 9532f9b62c1a833b0f714223e031bb00e3752dde.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, 2022-12-12 at 10:34 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17714
> Logged by: adarsh kumar
> Email address: ext-adarsh(dot)kumar(at)elisa(dot)fi
> PostgreSQL version: 13.5
> Operating system: Red Hat Enterprise Linux release 8.7 (Ootpa)
> Description:
>
> We are using Materialized view in our environment and the updates
> seem to be
> incremental in nature, i.e. data older that a specific date is not
> getting
> updated.
> we tried manual refresh also , but it does not seem to resolve the
> issue.
Are you able to provide a self-contained illustration of the problem in
SQL?
--
Jeff Davis
PostgreSQL Contributor Team - AWS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Francois Levesque | 2022-12-12 18:36:18 | Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum |
| Previous Message | David G. Johnston | 2022-12-12 16:38:26 | Re: BUG #17715: dumps file raise an error on restore if a materialized view use a function calling another function |