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 1qcAUf-00E6gr-W8 for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Sep 2023 20:11:50 +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 1qcAUd-00HD30-Dc for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Sep 2023 20:11:47 +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 1qcAUd-00HD2l-2y for pgsql-hackers@lists.postgresql.org; Fri, 01 Sep 2023 20:11:46 +0000 Received: from mail-lf1-x129.google.com ([2a00:1450:4864:20::129]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qcAUZ-002DAj-VZ for pgsql-hackers@postgresql.org; Fri, 01 Sep 2023 20:11:45 +0000 Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-5007616b756so4207483e87.3 for ; Fri, 01 Sep 2023 13:11:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693599101; x=1694203901; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=BK/PMi4BmGnPGbvMkiO91OpinosXdn9VzIT8hey9tRk=; b=QFFIcoVSeGHO04lU2pyAKdzXSiXDK5w9owusaZ5pDbPwwFxIEmSMVV/DWLglGupruW ViUiuOtJ2+/3yNCewfcI1CKUN/Xu7xpZ+QWAL5UycZt8Hx1wOtatvZJZJ5pWIWN71+rm ATBNnFP/W4HSWZOJGFxle6lIdjbnazySvjpKY3JFlXSVDVy4JL9p5SvtirWpjnv40bjl B7kQ1YqC+HEJ26qPdUoF4Bp3P06KXuHf/DootvWJjYd2SS49LDGJla0Br/BipIh/m98H +Z1SFvuBZBMaEpUgI4APorMYt7Yg/pesQ5Ww760myNwkjiDmvKOdDvh4ALfjdo9JHSrv oaIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693599101; x=1694203901; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=BK/PMi4BmGnPGbvMkiO91OpinosXdn9VzIT8hey9tRk=; b=Ej3OfIzwLx041W5c81vjlTD9qjymuhDkFIuNZRuXMK71co/SyGpkEdWvNgC+IINorM prHnZ5Y6CEvYTZhILpWEPcLCroMnZnUfa6w15K6YDN8KUEx/roWJMXjbbMdxoUhOYTF2 uy3cOfQs4VmvPcN/ftKL6/jo6JJNMtAAHF7CR1z08IndYb7/xvbj07zvGOqKYOOFTaBD zQh9jQRdx4fenjtrCTmHv3I717RpAIP4FwPjnLYIloYTiFod8LBxne9y+fX+GwMYAQ21 yvQlUhT7m3bEV4Oz+a1GlWAgcLYEd4+IpLLW6PSTQBDW8Mpbuyxayt1rGffiwiX6VuPU fmGA== X-Gm-Message-State: AOJu0YzHoUMcCwdP+VN1xXkwmBX1NurqTTqLgc2kWcsvwwRbTnvJAM+i lvIQc137lXG2CJDwYB9Xr5bKXIxiZkWZ1mnWFJU= X-Google-Smtp-Source: AGHT+IEkdznKOoyQZZoXcThiFmrBlHI9tBCFAOFhOC9ys+yZgU3Qx6NyiNfQivt/FNtKDWXlLVlBkyrZ+FnXTUCFwWw= X-Received: by 2002:a05:6512:3c8a:b0:500:aec8:cac1 with SMTP id h10-20020a0565123c8a00b00500aec8cac1mr2939782lfv.26.1693599101445; Fri, 01 Sep 2023 13:11:41 -0700 (PDT) MIME-Version: 1.0 References: <149ff9264db27cdf724b65709fbbaee4bf316835.camel@j-davis.com> <830a2bc6cbbb2e6e01c6c0d9f31f320822e10603.camel@j-davis.com> <63ceeec59ad6c07e17ce280e4bae31b65806ec06.camel@j-davis.com> In-Reply-To: <63ceeec59ad6c07e17ce280e4bae31b65806ec06.camel@j-davis.com> From: Robert Haas Date: Fri, 1 Sep 2023 16:11:30 -0400 Message-ID: Subject: Re: [17] CREATE SUBSCRIPTION ... SERVER To: Jeff Davis Cc: Joe Conway , Ashutosh Bapat , pgsql-hackers@postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Sep 1, 2023 at 4:04=E2=80=AFPM Jeff Davis wrote= : > On Thu, 2023-08-31 at 17:17 -0400, Joe Conway wrote: > > Maybe move postgres_fdw to be a first class built in feature instead > > of > > an extension? > > That could make sense, but we still have to solve the problem of how to > present a built-in FDW. > > FDWs don't have a schema, so it can't be inside pg_catalog. So we'd > need some special logic somewhere to make pg_dump and psql \dew work as > expected, and I'm not quite sure what to do there. I'm worried that an approach based on postgres_fdw would have security problems. I think that we don't want postgres_fdw installed in every PostgreSQL cluster for security reasons. And I think that the set of people who should be permitted to manage connection strings for logical replication subscriptions could be different from the set of people who are entitled to use postgres_fdw. --=20 Robert Haas EDB: http://www.enterprisedb.com