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 1qbN9k-00BqPr-2c for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Aug 2023 15:30:56 +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 1qbN9h-000TvS-Fg for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Aug 2023 15:30:53 +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 1qbN9h-000TvG-1X for pgsql-hackers@lists.postgresql.org; Wed, 30 Aug 2023 15:30:52 +0000 Received: from mail-pf1-x434.google.com ([2607:f8b0:4864:20::434]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qbN9c-001xTl-HK for pgsql-hackers@postgresql.org; Wed, 30 Aug 2023 15:30:52 +0000 Received: by mail-pf1-x434.google.com with SMTP id d2e1a72fcca58-68c0d4cc3a4so3571794b3a.1 for ; Wed, 30 Aug 2023 08:30:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20230601.gappssmtp.com; s=20230601; t=1693409446; x=1694014246; darn=postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=yJ8WVzZCzu9LpC8tXW/xq8aFeFhsCWFbXhDe28a+M/4=; b=hSWFWmZD0EwOVtTGfKX5LiiLPafTOWInbhtddtxwZi28MOy6Q1/u43YKtBd9AHQh1O J59OacLdb7fXf9p2tyPMnDArbg0bTkebETQ2iWe2pG7yyDC+UaBpb5sSQv03EBS3gHtz 4qN2sr84EI7KzoUbnQKedIBZ+33FYqJuE9OfKPKKEqA2/AcfPaT1xjh1Xhxcgx6tF2Cj ELQdQYUP2PJwMEc8iC1r5txR11DR/j14bJwWIBP62HBc6/g9Kr4kdGkNXU4FliUH6jtE mc/O+6YcuPa9yNXpXbjwHPhL/BBtsD6cpvzTHOQ9cx3OSVkePU4J+fG0sLR6mfsiZZxG hpYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693409446; x=1694014246; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=yJ8WVzZCzu9LpC8tXW/xq8aFeFhsCWFbXhDe28a+M/4=; b=EnDx1LI8mAIWrlPguT59mSDBRVt/tePrmGPdILonYCST2ELKRfXn11aPQb+v9sFg/i rymRULbQv1U1A8frSO3sJdHNr5AQYJnMAfNB4A7m1lTFfkTIlBhZqLFF9153tjSarLrg +kbagh07Xu2wjo0YSvQv5IOtTN360n6vZ16z6WRA7lT7WW3F8JQrlvKroHH0uqxTr5od QAes3p4oG+CNuac0uVWqAzsulbilxhr92+5qKYTR1KoluXihKU8QHGblweWvYPo70hnq /PdN9yKDKQ+z5+rlpHGbMJYNizkjajK1oKJ8gNmSnhcCjsoQAG6v52zN5OqViuPwNViE OQ8g== X-Gm-Message-State: AOJu0YxCOv0LGuZPEi07/j0Zv8KTU+P2FajpI3PAJSCjYIW5UptbyYen SloBGuv/NNRrJJOe0GyqPhMIkA== X-Google-Smtp-Source: AGHT+IGwgvnDjvHf+2JesDX+ZSTl3/zrrdRLzxEckzRh20X9OAp0m/Q3N7tOtLcHzrOAULGcJMyDlg== X-Received: by 2002:a17:90a:fb4c:b0:269:5b17:24b6 with SMTP id iq12-20020a17090afb4c00b002695b1724b6mr2379583pjb.9.1693409446105; Wed, 30 Aug 2023 08:30:46 -0700 (PDT) Received: from jeff-laptop.lan (c-98-45-81-55.hsd1.ca.comcast.net. [98.45.81.55]) by smtp.gmail.com with ESMTPSA id j14-20020a17090aeb0e00b002684b837d88sm1417845pjz.14.2023.08.30.08.30.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Aug 2023 08:30:45 -0700 (PDT) Message-ID: <830a2bc6cbbb2e6e01c6c0d9f31f320822e10603.camel@j-davis.com> Subject: Re: [17] CREATE SUBSCRIPTION ... SERVER From: Jeff Davis To: Ashutosh Bapat Cc: pgsql-hackers@postgresql.org Date: Wed, 30 Aug 2023 08:30:45 -0700 In-Reply-To: References: <149ff9264db27cdf724b65709fbbaee4bf316835.camel@j-davis.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4-0ubuntu2 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2023-08-30 at 19:11 +0530, Ashutosh Bapat wrote: > Are you suggesting that SERVERs created with FDW can not be used as > publishers? Correct. Without that, how would the subscription know that the FDW contains valid postgres connection information? I suppose it could create a connection string out of the options itself and do another round of validation, is that what you had in mind? > We can push down a join > between a replicated table and foreign table down to the foreign > server. Interesting idea. Regards, Jeff Davis