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 1qc9II-00E38N-H9 for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Sep 2023 18:54:58 +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 1qc9IG-00GhPu-Vh for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Sep 2023 18:54:56 +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 1qc9IG-00GhPf-HL for pgsql-hackers@lists.postgresql.org; Fri, 01 Sep 2023 18:54:56 +0000 Received: from mail-pl1-x62c.google.com ([2607:f8b0:4864:20::62c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qc9I8-002OiN-NY for pgsql-hackers@postgresql.org; Fri, 01 Sep 2023 18:54:55 +0000 Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-1c06f6f98c0so19040295ad.3 for ; Fri, 01 Sep 2023 11:54:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20230601.gappssmtp.com; s=20230601; t=1693594486; x=1694199286; 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=oWSqH2ncHJ5kMPYjgVA9uiQ0t44BQZGCUr1+P8UZb5c=; b=Y9xIV7JecLPOZeI3EdYgS6w+uplzy40gyPWrPtZZ761XwS7jltjnw/ccmNqqDHinzy +H9pBt42geqf/1PtbGxU6A/uFTMtknuOCPvGQ1XctUJtXn5sm4sAxksIoIGNBED0CGYG mPHIscCthtHBndn3mS6TfCGruH6noNWdExe29cam/kN6L56BZcQBuw/wtagtXwxCx7tr qGvB9V0Tdi0KVHrH1t22A+cS8xwV0tK5rfimdsd/iACxI2c6PFJkA/RIfRM5EA1xA+Ne v8pGzG39Gy80N5pUsnDBOAOmoLOWEj9lP5CLhcajGDcdp6apZoLTGIMfiwkY27WQGJAF 06Pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693594486; x=1694199286; 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=oWSqH2ncHJ5kMPYjgVA9uiQ0t44BQZGCUr1+P8UZb5c=; b=KhFT1QPoI3JTI3++olqojaF4TlGYrqBzI2fco6lZkLa4Xt3cndB48HqnxwElsBAxpO p2Ub3FZy92NUr/gRQ84SC8uBkJGhTW1WvtPCAz3hcyjg+/BCIVAI8F6b2r/bYCTIENiI 6GOaoq41R1qpzKq3nXEPnOQ3i+46XBfyaoZ2EuspeRTU4F61zUfjLvCfSLaKMyGxbSQ+ IgsLVV2uBvQMY1MuHev1IfZ4rVmyks5ec1qQB66FkEQNpooCWVoVCP8EK1xqtqfhRyrA t+MGtD+qZo8+SF+CXZROXQjSiC2UA+QWXBXqrCKRrd/ossrOLu6oMA3l9yKNv+kDshLP FOVg== X-Gm-Message-State: AOJu0Yx2TAuMeQvVSwMoTbwOsxzzz6MuLCAZo2gK0fGtWgarjVJwaqNb F+COr9f2fIwgp/ww5zFqXMnp1Q== X-Google-Smtp-Source: AGHT+IFY1ZNkNB0HT+qjAPeQUYUz+s5cedeCfq6bJzKtwF8U0KvPuxc2Wdog2yfnYmuHt8yUqAiccQ== X-Received: by 2002:a17:903:2281:b0:1bf:a41:371e with SMTP id b1-20020a170903228100b001bf0a41371emr4269395plh.56.1693594486219; Fri, 01 Sep 2023 11:54: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 jc17-20020a17090325d100b001bb0eebd90asm3280656plb.245.2023.09.01.11.54.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 01 Sep 2023 11:54:45 -0700 (PDT) Message-ID: <433d0845248e86c0317d9d396926182cfe157340.camel@j-davis.com> Subject: Re: [17] CREATE SUBSCRIPTION ... SERVER From: Jeff Davis To: Ashutosh Bapat , Joe Conway Cc: pgsql-hackers@postgresql.org Date: Fri, 01 Sep 2023 11:54:44 -0700 In-Reply-To: References: <149ff9264db27cdf724b65709fbbaee4bf316835.camel@j-davis.com> <830a2bc6cbbb2e6e01c6c0d9f31f320822e10603.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 Fri, 2023-09-01 at 12:28 +0530, Ashutosh Bapat wrote: > Thinking larger, how about we allow any FDW to be used here. That's a possibility, but I think that means the subscription would need to constantly re-check the parameters rather than relying on the FDW's validator. Otherwise it might be the wrong kind of FDW, and the user might be able to circumvent the password_required protection. It might not even be a postgres-related FDW at all, which would be a bit strange. If it's constantly re-checking the parameters then it raises the possibility that some "ALTER SERVER" or "ALTER USER MAPPING" succeeds but then subscriptions to that foreign server start failing, which would not be ideal. But I could be fine with that. > But I think there's some value in bringing > together these two subsystems which deal with foreign data logically > (as in logical vs physical view of data). I still don't understand how a core dependency on an extension would work. Regards, Jeff Davis