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 1rxeJx-00AX5n-TW for pgsql-general@arkaria.postgresql.org; Fri, 19 Apr 2024 02:49:49 +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 1rxeJv-00Dg4F-9j for pgsql-general@arkaria.postgresql.org; Fri, 19 Apr 2024 02:49:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rxeJu-00Dg46-Sv for pgsql-general@lists.postgresql.org; Fri, 19 Apr 2024 02:49:46 +0000 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rxeJs-001j0p-Ax for pgsql-general@lists.postgresql.org; Fri, 19 Apr 2024 02:49:46 +0000 Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-518a3e0d2ecso2395982e87.3 for ; Thu, 18 Apr 2024 19:49:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713494982; x=1714099782; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=xgrbi1HMkx2kgBr1bq9u0Nsl+HcRqBo7UlbZZxTMrCU=; b=WEgAuw4yYw0tZWlhxsas5B6lb0YMeFbV3uHlwdYV3GdbwxXSzqAjpTdC6mVA+NjXqh C4rlxNzaDNNJdZe6mPBFnzhVks0LLdrIXJa4G287twtgfOTFn4Xucfw2CKqwr5WxL0o9 g/272C0MUBqxnLJwTH0By7BybtgP0UHyf+VBNWE8JYX0xjfJDh5Po0MfwLBvgTBfkPoe K1qoDum4qsGEAXdjjc6fGegpMy+rfulL9jmQoVABWNs6MHlMa+5VaQi7/iomy5UUxq4g h2p4dP0YtG5eHaPIFP8MHl7KUQnyUKu6AkIXXy08eEJO9S4fd3CNSrlOBW6gOWWi6JrJ 48wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713494982; x=1714099782; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=xgrbi1HMkx2kgBr1bq9u0Nsl+HcRqBo7UlbZZxTMrCU=; b=PyH5yigigiCtHWmvfrtHoB0nuudkdFEJnR8jxhvHMdKaJDnHk1tbGYt7F0qggdq3tg mTyZEVWXbf2eVDobasz0y7mnhpX4EO+VuKcoOdUiVt9bBkm98KD8+/qsJzOcXA+9CfUr uEfmeoXEk+MwuTvQv7TNekR6xbSBlI3x9uU5yW3Dx7PkWVDzz6wevJ6vDCumGfJe4S0H dKS4rXqm3m0zR+I7LUM02j8HnkXI8uNGrDPWTJUX/wJAcHqEaavPMhnd1011e4hgpFT6 Vku3alOO82nZ6K9lBfH0Czlvxu+nRmctrj12T0hZMVRwEnYJPA/xIEhqDVwxOqfz3QUW Mdvg== X-Gm-Message-State: AOJu0YwCfVdHj6gvE4Sy1Fa0gRMs/eKKdC2Fi2pVpjDCjmTbBHdDW5SU RWj10j4zf1NNEcGYbuMXjC8uw+Oi5E88TGlpUv8zf14vlX7MVYYDWFNrhitXpe08yJgu2qCI1fj Zi7qmPxq3fZ9uWUhdLRnISXwoV2KGvw== X-Google-Smtp-Source: AGHT+IF4Xm0Cey3H3LIZj3UtQYNkLuZyUca2V9W1o1u28vjo5rRJS5BTPNLnyW7NwO8dgCF7wGc3I2iYufVn0YWhbKY= X-Received: by 2002:ac2:529c:0:b0:515:d196:6d4d with SMTP id q28-20020ac2529c000000b00515d1966d4dmr550615lfm.24.1713494981813; Thu, 18 Apr 2024 19:49:41 -0700 (PDT) MIME-Version: 1.0 From: Michael Nolan Date: Thu, 18 Apr 2024 21:49:31 -0500 Message-ID: Subject: Can you refresh a materialized view from a materialized view on another server? To: "pgsql-generallists.postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 server.) Mike Nolan htfoot@gmail.com