Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vvlfi-000zoX-0J for pgsql-general@arkaria.postgresql.org; Fri, 27 Feb 2026 00:25:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vvlff-00Ginz-2y for pgsql-general@arkaria.postgresql.org; Fri, 27 Feb 2026 00:25:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vvlfe-00GinX-2T for pgsql-general@lists.postgresql.org; Fri, 27 Feb 2026 00:25:31 +0000 Received: from fhigh-a2-smtp.messagingengine.com ([103.168.172.153]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vvlfb-00000001OHn-2ZK8 for pgsql-general@lists.postgresql.org; Fri, 27 Feb 2026 00:25:29 +0000 Received: from phl-compute-05.internal (phl-compute-05.internal [10.202.2.45]) by mailfhigh.phl.internal (Postfix) with ESMTP id 635731400247; Thu, 26 Feb 2026 19:25:27 -0500 (EST) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-05.internal (MEProxy); Thu, 26 Feb 2026 19:25:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1772151927; x=1772238327; bh=Uwa36v6weA8v/lC5C2lIoronWm7WXjManhWfPWDWfQw=; b= QOf18Bid05y33BpAfBV61FMneqqOSHKGHV8YmzM/5hMo7Onv8DrvY3DfWQjrMzxt pI8/JJiQ6cgWVwl8hbM7IY9uNUZTs7ScqdViCDhm1WV0pe8fkDx2h92dcv2Tl81T t5p8f3/YBRd1dXAoG1PPVWSsa+Gao7EkOs9ulqyyT0bPwR4Aj494VH7sbspzVkTy czvbDugbfXrvu69VyTKLq4TsWK2OnHg6YSEIDXdxBB0BHaHW69LiWme8PqXglRNh gciOr8qmJYERm26/NPbqnKNkL9UR/+HS2F7OJQg7dmZ6JOlt4E0ikMLxRCvBXVb6 RtyR5tJF1tX7jS43uNpdJg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1772151927; x= 1772238327; bh=Uwa36v6weA8v/lC5C2lIoronWm7WXjManhWfPWDWfQw=; b=P 8EyDCLCz+Iqof78TXYDwQyuzc+ycIM0nJYKHWWf9uX4rZ/ajC4NmXrDRXUe/ReP8 90/MMlW11oS+qoRDF8W2RD5VfFTXGNBl2EQlS+H+w9iBM2slPvVUME+FCetmnptw 8Dhv6CBXr5tEbI7IzN2FOwZ++n72AU5ndYG8KbmOuuUP6t7pnp+JLyKfH+Jk4K1n Icqxvpt6rVEP22NeneWoUuQTA2/iJAjE133JryIu+sh3X0n37T9XuQDX83AvPwZK I9e9NXdMMrvM9zuyx+7rmYwP70UPHo/OPGl8RVT8jONt3QHSN3d9OTtXnQ+sRCOq uKdGSeI3Xscv78v1Wj4wg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgddvgeejheefucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughrihgr nhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh eqnecuggftrfgrthhtvghrnhepfeegfeeiuedtgffgteeggfehkeejheetieeliefgteei keejvdeiveeigfehvedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgs pghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohephhhtfhhooh htsehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrhgrlheslhhi shhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 26 Feb 2026 19:25:26 -0500 (EST) Message-ID: <825efe68-74e5-44e5-ae86-e4f27b8fead5@aklaver.com> Date: Thu, 26 Feb 2026 16:25:25 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Issue with refreshing materialized view from another system To: Michael Nolan Cc: "pgsql-generallists.postgresql.org" References: <7f97d4a8-1f3f-47b1-8c42-5e0b8c46d467@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 > 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 > > htfoot@gmail.com > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > -- Adrian Klaver adrian.klaver@aklaver.com