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 1qby8R-00DTtT-KI for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Sep 2023 07:00:03 +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 1qby7Q-00Cbvk-6Y for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Sep 2023 06:58:59 +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 1qby7P-00CbvU-Qh for pgsql-hackers@lists.postgresql.org; Fri, 01 Sep 2023 06:58:59 +0000 Received: from mail-ua1-x92f.google.com ([2607:f8b0:4864:20::92f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qby7M-002I7m-Qm for pgsql-hackers@postgresql.org; Fri, 01 Sep 2023 06:58:59 +0000 Received: by mail-ua1-x92f.google.com with SMTP id a1e0cc1a2514c-79414715edeso488762241.0 for ; Thu, 31 Aug 2023 23:58:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693551534; x=1694156334; 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=zhK2sdceP1MmtqrNWrCzaOve2zZSJvaRwGJ3RC++FcE=; b=bPnLS5HhSxUxTdfqB+joctvx7fGV2Vg0vaouJo+Xjv1LLdoFO8CE5tj8ut9hGTKqfb MfbTdcPZey22frvGifSOWIFCSbNgae9NnAE8qNAWy0B/yfc0tyAtucnFog0MXiet5yEt C305Jiqiv65HF63K6hh3zlWYIQWU27ztFbsACYB4n+yNr3/LmSMTcVvSafKzypziRyM9 +GAMW5ubphJ6QghKn3IAacSW990pWYmdR1o7B4Z9VZOiyVoxtzeNixqi3s/yRbR+I5zJ K0BPzNLKSq7Bg3HhMvc+O68t5E8m1Q+ObRA8ZHaz/LNXZOGBDTZnPeL0xmMzceeOCGEv BrSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693551534; x=1694156334; 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=zhK2sdceP1MmtqrNWrCzaOve2zZSJvaRwGJ3RC++FcE=; b=jD940pGaIOotOuv3+0F6yHbQVXzyIdiidUYV/bMDKeIDYrgstNBidD9jwIyfSgul1T NuvHxlvyQK7iMOBo5PpGl3YfbTT+hIidIjGEy/730k7ZqqruAiOGKIrDvcOAxB8k9ms2 9MfL1zmlDMDsepKtgLDhMoPiATFiqwd27ZEC0WF0UIlHicnwK3wgp20EEGCqeQnCGQ5l CswyqKyoy/Mfr+eiT2ievokrsWIrb3C0clM2O0haL8eKvP0EkObYWRFBWyNpdncCKtPM 0hnJPI/5NR1f1bz/LHqCekc7Vx0sTssJ1wgjsjqDxHZc42amKcoD5iXJUsQVJBQ6qQC0 SEdQ== X-Gm-Message-State: AOJu0Yy82qHVg/wOv5d5frC9GsKZUjqdrT3lKsWUbm4Rii2fF2XvogOM UY3HX5fZNbgjNLr1BorOcLAQcNk+Xk6Tr60iWjE= X-Google-Smtp-Source: AGHT+IEgjcjUeNqG61Ku2LTTy77cc9pcgAZqnBcCDwTJ0P5w4zh66fYujxYVHTzOvmoL61qlsUCb5CjPYv5j5iJEWP0= X-Received: by 2002:a67:e98f:0:b0:44e:8ef9:3370 with SMTP id b15-20020a67e98f000000b0044e8ef93370mr1541370vso.5.1693551534477; Thu, 31 Aug 2023 23:58:54 -0700 (PDT) MIME-Version: 1.0 References: <149ff9264db27cdf724b65709fbbaee4bf316835.camel@j-davis.com> <830a2bc6cbbb2e6e01c6c0d9f31f320822e10603.camel@j-davis.com> In-Reply-To: From: Ashutosh Bapat Date: Fri, 1 Sep 2023 12:28:43 +0530 Message-ID: Subject: Re: [17] CREATE SUBSCRIPTION ... SERVER To: Joe Conway , Jeff Davis Cc: 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 2:47=E2=80=AFAM Joe Conway wrot= e: > > On 8/31/23 12:52, Jeff Davis wrote: > > On Thu, 2023-08-31 at 10:59 +0530, Ashutosh Bapat wrote: > >> The server's FDW has to be postgres_fdw. So we have to handle the > >> awkward dependency between core and postgres_fdw (an extension). > > > > That sounds more than just "awkward". I can't think of any precedent > > for that and it seems to violate the idea of an "extension" entirely. > > > > Can you explain more concretely how we might resolve that? > > > Maybe move postgres_fdw to be a first class built in feature instead of > an extension? Yes, that's one way. Thinking larger, how about we allow any FDW to be used here. We might as well, allow extensions to start logical receivers which accept changes from non-PostgreSQL databases. So we don't have to make an exception for postgres_fdw. 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). --=20 Best Wishes, Ashutosh Bapat