public inbox for [email protected]
help / color / mirror / Atom feedRe: Issue with refreshing materialized view from another system
2+ messages / 2 participants
[nested] [flat]
* Re: Issue with refreshing materialized view from another system
@ 2026-02-26 23:37 Michael Nolan <[email protected]>
2026-02-26 23:45 ` Re: Issue with refreshing materialized view from another system Ron Johnson <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Michael Nolan @ 2026-02-26 23:37 UTC (permalink / raw)
To: Adrian Klaver <[email protected]>; +Cc: pgsql-generallists.postgresql.org <[email protected]>
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 PM Adrian Klaver <[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]>
>
>
> --
> Adrian Klaver
> [email protected]
>
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Issue with refreshing materialized view from another system
2026-02-26 23:37 Re: Issue with refreshing materialized view from another system Michael Nolan <[email protected]>
@ 2026-02-26 23:45 ` Ron Johnson <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Ron Johnson @ 2026-02-26 23:45 UTC (permalink / raw)
To: pgsql-generallists.postgresql.org <[email protected]>
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 PM Michael Nolan <[email protected]> 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.
>
> Mike Nolan
>
> On Thu, Feb 26, 2026 at 4:11 PM Adrian Klaver <[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]>
>>
>>
>> --
>> Adrian Klaver
>> [email protected]
>>
>
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-02-26 23:45 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-02-26 23:37 Re: Issue with refreshing materialized view from another system Michael Nolan <[email protected]>
2026-02-26 23:45 ` Ron Johnson <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox