On 2/26/26 3:37 PM, Michael Nolan wrote:
My understanding is that the mysql server is at a Linode facility in PA,
the current production postgres server is in Asheville NC, and the
intended new server is a Azure server in the eastern US, not sure
exactly where.
The two small matviews refresh, the two bigger ones fail, so it seems
size-related, which is why I was wondering if the settings might make a
difference because this server isn't fully production-scale yet. But
weve transferred 175 GB files to it in about 6 hours so I think the net
connection itself is probably not the issue.
1) If my math is right that works out to 8.1 MB/s. Testing
here(Bellingham WA) to my Linode in Fremont CA I get somewhere around an
average of 65 MB/s download/upload. Not saying this is the issue, but
you might want to test network speed between your current server and new
server to the MySQL server.
2) Is there an error raised in the Postgres logs?
3) What are the 'hardware' specifications for the Azure server vs the
existing(Linode?) one?
4) Define small view vs large view.
Mike Nolan
On Thu, Feb 26, 2026 at 4:11 PM Adrian Klaver <[email protected]
<mailto:[email protected]>> wrote:
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
> [email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
--
Adrian Klaver
[email protected] <mailto:[email protected]>
--
Adrian Klaver
[email protected]
