MIME-Version: 1.0
References: <CAOzAquKm3DzMA3bdW5obh+ZWjuFJ=y9n4Wg7d=qFfkOXf0tHoA@mail.gmail.com>
 <7f97d4a8-1f3f-47b1-8c42-5e0b8c46d467@aklaver.com>
In-Reply-To: <7f97d4a8-1f3f-47b1-8c42-5e0b8c46d467@aklaver.com>
From: Michael Nolan <htfoot@gmail.com>
Date: Thu, 26 Feb 2026 17:37:34 -0600
Message-ID: <CAOzAquLVSry4UbiVJDG=RtoVNabiMbXZ=cmCOKa=Foa_sbhauw@mail.gmail.com>
Subject: Re: Issue with refreshing materialized view from another system
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000a4fef1064bc29b17"
Archived-At: <https://www.postgresql.org/message-id/CAOzAquLVSry4UbiVJDG%3DRtoVNabiMbXZ%3DcmCOKa%3DFoa_sbhauw%40mail.gmail.com>
Precedence: bulk

--000000000000a4fef1064bc29b17
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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.

Mike Nolan

On Thu, Feb 26, 2026 at 4:11=E2=80=AFPM Adrian Klaver <adrian.klaver@aklave=
r.com>
wrote:

> On 2/26/26 1:59 PM, Michael Nolan wrote:
> > We have a connection from a PostgreSQL server to a MySQL server which i=
s
> > 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 th=
e
> > 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@gmail.com <mailto:htfoot@gmail.com>
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>

--000000000000a4fef1064bc29b17
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>My understanding is that the mysql server is at a Lin=
ode 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 su=
re exactly where.</div><div><br></div><div>The two small matviews refresh, =
the two bigger ones fail, so it seems size-related, which is why I was wond=
ering if the settings might make a difference because this server isn&#39;t=
 fully production-scale yet.=C2=A0 But weve=C2=A0transferred 175 GB files t=
o it in about 6 hours so I think the net connection itself is probably not =
the issue.</div><div><br></div><div>Mike Nolan</div></div><br><div class=3D=
"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Thu, Feb 26, 2026 at 4:11=E2=80=AFPM Adrian Klaver &lt;<a href=3D"mailto:=
adrian.klaver@aklaver.com">adrian.klaver@aklaver.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">On 2/26/26 1:59 PM, Mic=
hael Nolan wrote:<br>
&gt; We have a connection from a PostgreSQL server to a MySQL server which =
is <br>
&gt; used to update a materialized view on the PostgreSQL server from table=
s <br>
&gt; on the MySQL server (running CIVI-CRM, which may not be relevant.)<br>
&gt; <br>
&gt; We are trying to move the PostgreSQL server=C2=A0to a new cloud server=
.<br>
&gt; <br>
&gt; On the current production system, all the materialized views work, but=
 <br>
&gt; the biggest of them can take about an hour.<br>
&gt; <br>
&gt; On the new system, the smallest of the materialized views works, but t=
he <br>
&gt; larger ones all seem to time out.<br>
<br>
&quot;... move the PostgreSQL server to a new cloud server&quot;, where is =
that <br>
relative to the MySQL server compared to old Postgres server?<br>
<br>
&gt; <br>
&gt; Could this be some kind of setting on PostgreSQL, like a memory or <br=
>
&gt; buffer issue?<br>
&gt; <br>
&gt; Mike Nolan<br>
&gt; <a href=3D"mailto:htfoot@gmail.com" target=3D"_blank">htfoot@gmail.com=
</a> &lt;mailto:<a href=3D"mailto:htfoot@gmail.com" target=3D"_blank">htfoo=
t@gmail.com</a>&gt;<br>
<br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klave=
r@aklaver.com</a><br>
</blockquote></div>

--000000000000a4fef1064bc29b17--