MIME-Version: 1.0
References: <CAOzAquKm3DzMA3bdW5obh+ZWjuFJ=y9n4Wg7d=qFfkOXf0tHoA@mail.gmail.com>
 <7f97d4a8-1f3f-47b1-8c42-5e0b8c46d467@aklaver.com> <CAOzAquLVSry4UbiVJDG=RtoVNabiMbXZ=cmCOKa=Foa_sbhauw@mail.gmail.com>
 <CANzqJaBOOxsH4VE5Hk=si0_Drz1chRKxuebBQru9kWkbBi0E0w@mail.gmail.com>
In-Reply-To: <CANzqJaBOOxsH4VE5Hk=si0_Drz1chRKxuebBQru9kWkbBi0E0w@mail.gmail.com>
From: Michael Nolan <htfoot@gmail.com>
Date: Thu, 26 Feb 2026 17:48:11 -0600
Message-ID: <CAOzAquK-eUGYRRz1s9djD+jC-WDdnOZ6EyKAxoD_LkrcrYF+1A@mail.gmail.com>
Subject: Re: Issue with refreshing materialized view from another system
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000007e9cfc064bc2c12d"
Archived-At: <https://www.postgresql.org/message-id/CAOzAquK-eUGYRRz1s9djD%2BjC-WDdnOZ6EyKAxoD_LkrcrYF%2B1A%40mail.gmail.com>
Precedence: bulk

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

I can run select statements on the mysql server from the azure server, but
the command we're using to refresh the matview is:
REFRESH MATERIALIZED VIEW memmast_ratings;

Mike Nolan

On Thu, Feb 26, 2026 at 5:45=E2=80=AFPM Ron Johnson <ronljohnsonjr@gmail.co=
m> wrote:

> Mike,
>
> 1. You're using mysql_fdw to connect?
>
> 2. What happens when you just run the raw SELECT statement (redirecting
> stdout to /dev/null, since we only need timings and error messages) from
> psql?
>
>
> On Thu, Feb 26, 2026 at 6:37=E2=80=AFPM Michael Nolan <htfoot@gmail.com> =
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 inten=
ded
>> 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@akl=
aver.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
>>> 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, bu=
t
>>> > 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@gmail.com <mailto:htfoot@gmail.com>
>>>
>>>
>>> --
>>> Adrian Klaver
>>> adrian.klaver@aklaver.com
>>>
>>
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>

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

<div dir=3D"ltr"><div>I can run select statements on the mysql server from =
the azure server, but the command we&#39;re using to refresh=C2=A0the matvi=
ew is:</div><div>REFRESH MATERIALIZED VIEW memmast_ratings;<br><br></div><d=
iv>Mike Nolan</div></div><br><div class=3D"gmail_quote gmail_quote_containe=
r"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 26, 2026 at 5:45=E2=80=
=AFPM Ron Johnson &lt;<a href=3D"mailto:ronljohnsonjr@gmail.com">ronljohnso=
njr@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr"><div>Mike,</div><div><br></div><div>1. You=
9;re using mysql_fdw to connect?</div><div><br></div><div>2. What happens w=
hen you just run the raw SELECT statement (redirecting stdout to /dev/null,=
 since we only need timings and error messages) from psql?</div><div><br></=
div><div><br></div><div dir=3D"ltr">On Thu, Feb 26, 2026 at 6:37=E2=80=AFPM=
 Michael Nolan &lt;<a href=3D"mailto:htfoot@gmail.com" target=3D"_blank">ht=
foot@gmail.com</a>&gt; wrote:</div><div class=3D"gmail_quote"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>My understanding=
 is that the mysql server is at a Linode facility in PA, the current produc=
tion postgres server is in Asheville NC, and the intended new server is a A=
zure server in the eastern US, not sure 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 wondering if the settings might make a dif=
ference because this server isn&#39;t fully production-scale yet.=C2=A0 But=
 weve=C2=A0transferred 175 GB files to it in about 6 hours so I think the n=
et connection itself is probably not the issue.</div><div><br></div><div>Mi=
ke Nolan</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Thu, Feb 26, 2026 at 4:11=E2=80=AFPM Adrian Klaver &lt;<=
a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klaver=
@aklaver.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">On 2/26/26 1:59 PM, Michael 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>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature"><div dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div=
>Don&#39;t boil me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobs=
ter!</div></div></div></div></div></div>
</blockquote></div>

--0000000000007e9cfc064bc2c12d--