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.94.2) (envelope-from ) id 1rxpXM-00CIG4-QV for pgsql-general@arkaria.postgresql.org; Fri, 19 Apr 2024 14:48:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rxpXJ-0036pS-Eg for pgsql-general@arkaria.postgresql.org; Fri, 19 Apr 2024 14:48:21 +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.94.2) (envelope-from ) id 1rxpXJ-0036pK-43 for pgsql-general@lists.postgresql.org; Fri, 19 Apr 2024 14:48:21 +0000 Received: from wfhigh2-smtp.messagingengine.com ([64.147.123.153]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rxpXF-003d8n-QK for pgsql-general@lists.postgresql.org; Fri, 19 Apr 2024 14:48:19 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfhigh.west.internal (Postfix) with ESMTP id 22BD11800143; Fri, 19 Apr 2024 10:48:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Fri, 19 Apr 2024 10:48:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= 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=1713538094; x=1713624494; bh=h60xzRbY8Rv5pGN7A7FwVCG+X0ouL9pyqKBSgFeL5DU=; b= iU+A80NQmthjAOcuA1EcOKw7Tuy+45/OmaQeJLFmV9ZjvPGrl7Nib/14ufo3lPLB pu49ZQmAFwOhjC+5yDRdyhy8wrcq1ixYN34jOW8xc11wdI1A2E95JtUCDeqp5BLv pv+HQbaqECV8BDQT3mO+7Ah4RT2zEVsxiCTw+J34oQlcbWw14KbdQutjs7RO0iCI NtAJQGRUZMXbsUV5rmMRSyYokWR/Lvqi4ikCn7ZZPXq5lT8dNi9qrRtaWrEcdjUn 6U6Sea8KBIjdEtLZ6oy14RVSVPcq/eF+Hc1BjZUUXEKn2qnuWdoqGkA0iezOz+tP ksT/L9nQWwld9UYTTAKZWg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1713538094; x= 1713624494; bh=h60xzRbY8Rv5pGN7A7FwVCG+X0ouL9pyqKBSgFeL5DU=; b=d hFmEfMjWflBHsPVI17t2u17tphdDV8XjnFOCnJU2DlAUj7ypZPBI3FRBqi/lNZiy wIwkgxUYONgMyOsWDe8X4MCM1EV6zwqxKx1hc+mXAxUJmpu9Di58gMebzhThz5p9 mqffaN1gy9DTblgq591LgXPlWORWR44kCNdcsL+5zvUKpMd+i3wSC3z35Guvu7vK 5dpJ6SOQemKJZebcOMNj5GVQR7PjX0ocOBGIQwipSUncN7VZouBawtUpSMUAPpw9 r7G9KagTHUcOtRbV7oWMqDG4BcZ3x/F5GgyOXM44c68wbfRg9fKRBKljQsX5mel6 MYxcUQgeqs//R2ArBDv+Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudekvddgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeeivdfhieehheegueeileejieettdejhedugeefleek vdelkeehtdfgiefffeekudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 19 Apr 2024 10:48:13 -0400 (EDT) Message-ID: <0f5afc0e-4c62-429a-853e-75605d49b7e5@aklaver.com> Date: Fri, 19 Apr 2024 07:48:13 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Can you refresh a materialized view from a materialized view on another server? To: Michael Nolan , "pgsql-generallists.postgresql.org" References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 4/18/24 19:49, Michael Nolan wrote: > My production server has a materialized view that is refreshed from a > mysql_fdw several times a day. > > What I'd like to be able to do is refresh the materialized view on the > testbed server from the one on the production server so that they are > the same. (Refreshing it from the MySQL server will result in one > that has records that have been added or updated rather than an exact > copy of the one on the production serve Use postgres_fdw to connect the test bed to the production server? > > Mike Nolan > htfoot@gmail.com > > -- Adrian Klaver adrian.klaver@aklaver.com