| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Michael Nolan <htfoot(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Issue with refreshing materialized view from another system |
| Date: | 2026-02-26 22:11:06 |
| Message-ID: | 7f97d4a8-1f3f-47b1-8c42-5e0b8c46d467@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/26/26 1:59 PM, Michael Nolan wrote:
> We have a connection from a PostgreSQL server to a MySQL server which is
> used to update a materialized view on the PostgreSQL server from tables
> on the MySQL server (running CIVI-CRM, which may not be relevant.)
>
> We are trying to move the PostgreSQL server to a new cloud server.
>
> On the current production system, all the materialized views work, but
> the biggest of them can take about an hour.
>
> On the new system, the smallest of the materialized views works, but the
> larger ones all seem to time out.
"... move the PostgreSQL server to a new cloud server", where is that
relative to the MySQL server compared to old Postgres server?
>
> Could this be some kind of setting on PostgreSQL, like a memory or
> buffer issue?
>
> Mike Nolan
> htfoot(at)gmail(dot)com <mailto:htfoot(at)gmail(dot)com>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Nolan | 2026-02-26 23:37:34 | Re: Issue with refreshing materialized view from another system |
| Previous Message | Michael Nolan | 2026-02-26 21:59:54 | Issue with refreshing materialized view from another system |