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 1sMrIi-00563i-6q for pgsql-general@arkaria.postgresql.org; Thu, 27 Jun 2024 15:44:44 +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 1sMrIg-00BMNx-HR for pgsql-general@arkaria.postgresql.org; Thu, 27 Jun 2024 15:44:42 +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 1sMrIg-00BMNn-73 for pgsql-general@lists.postgresql.org; Thu, 27 Jun 2024 15:44:42 +0000 Received: from mail-qv1-xf2f.google.com ([2607:f8b0:4864:20::f2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sMrIe-003qSr-Bh for pgsql-general@lists.postgresql.org; Thu, 27 Jun 2024 15:44:41 +0000 Received: by mail-qv1-xf2f.google.com with SMTP id 6a1803df08f44-6b4fdf56903so31448806d6.1 for ; Thu, 27 Jun 2024 08:44:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719503079; x=1720107879; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=clPzNP2qbuX19AklsFzGHA7D8ANSSdK9cwW3N4TWUc0=; b=GvqrWAxO6ijA1gXcFvHkB54TiYTvSvCkeDbDSNUkUcRN/FTAB+/PetrvLwtqfoTy5A GpZmtVAkSE9FJT5VEaZ2Of80FZf4APFo0cbr3vT7NcVoFzvRYKE98v5rYK2uNNGnNYVW zDXTE3eS4lkPHyourgo9GzHrQTBdn2vVhoOrDFfjMF9SOq/nQNFNudnIlT1EK0kqjKX5 AcbOedrWKxUbVk78XCANmleT/cH8fDoW3eiFZmDZP9VwZfyqcUf4DXqd5JEkdyN18x/X Ql+6gMsYywRPFjnWaRufMGQ+ziWgKytfnr0TOeZxQOPfW3Nugu2uLO91tm5QdXO0opoT A1nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719503079; x=1720107879; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=clPzNP2qbuX19AklsFzGHA7D8ANSSdK9cwW3N4TWUc0=; b=AKBBXd61J/A//t0ihbbZTYRCjf9AqcbtHRG5PrTVSyhayxSe5JHRaTRNPMm/H/i1Y/ BR7dfbPrtJuappFNmZUS5fCEKW66J+HpD3f+F95C+GOmwaMxm4RkU2zIVs6XGy0y7WtC LjDBiu5OsnIwLWA/Ys3JBHNv84Od4NsHD2VZL/XAGgAdSSTd1j85G9Q0i+vvYreq4qpi 8PppVx5A/KcRy1PZeU7sLjSlLy5crKmQoD39j/cPAQj0XcCjpsPummmhx++YlVYc3w7X 24mg5fP9TQTVnwVQRskMuP4MayeUyQLXxls4BSotNfTBDiB4loU0RqK3ZdqMi8KpW6KE ILfA== X-Gm-Message-State: AOJu0YzG6A5Pq/y41wyOY9EtavBaQ1DCftXp9tsUNZagHYPsl2/qicEU a6gnB5mPz33NEKqWjgEbXY9/ycM+HmdFAGAJJC1bexE0u/sD7TofJQuFUhtf58uNw//xI1qGurd xzNZd9MCc/I5kevTfMnBfZDWrPecqfQ== X-Google-Smtp-Source: AGHT+IG9kFpfZVI1aJuiNMo79p71gt4GGrgaeJoxa4cicEC9miLM2Fmx/NZGWijYNiK1qu8KhBXQ0Vg2GmGH9TmzJto= X-Received: by 2002:a0c:f3c5:0:b0:6b0:763c:e069 with SMTP id 6a1803df08f44-6b5409bf286mr128457436d6.18.1719503078723; Thu, 27 Jun 2024 08:44:38 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6214:2628:b0:6b0:822a:8583 with HTTP; Thu, 27 Jun 2024 08:44:37 -0700 (PDT) In-Reply-To: <609c8cd402e145e2af12bcfe20ac22e1@NetCracker.com> References: <609c8cd402e145e2af12bcfe20ac22e1@NetCracker.com> From: "David G. Johnston" Date: Thu, 27 Jun 2024 08:44:37 -0700 Message-ID: Subject: Re: dblink Future support vs FDW To: Dhritman Roy Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000329a65061be10282" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000329a65061be10282 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thursday, June 27, 2024, Dhritman Roy wrote: > > This is my attempt to seek support at PostGreSQL.So, if I have broken any > protocols/rules or violated any code of conduct then please do forgive an= d > guide me. Thanks. > > The G is not capitalized. > I know we can use FDW but our teams are right now considering dblink ( it > seems it is more performant when compared to FDW ) and we obviously do no= t > want to end up in a situation where we develop something in few months an= d > then we find that the PostGreSQL support is ending with a new version. > There is no deprecation note and they have co-existed for years now. Lacking the former, it isn=E2=80=99t going to just be removed for no reason= , and there presently exists no reason to remove it. I cannot predict the future though. But IME it is exceedingly unlikely to happen. David J. --000000000000329a65061be10282 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thursday, June 27, 2024, Dhritman Roy <dhritman.roy@netcracker.com> wrote:=C2=A0

This is my attempt to seek support at PostGreSQL.So,= if I have broken any protocols/rules or violated any code of conduct then = please do forgive and guide me. Thanks.


The G is not capitalized.
=C2=A0

I know we can use FDW but our teams are right now co= nsidering dblink ( it seems it is more performant when compared to FDW ) an= d we obviously do not want to end up in a situation where we develop someth= ing in few months and then we find that the PostGreSQL support is ending with a new version.

=C2=A0
There is no deprecation note and they have co-e= xisted for years now.=C2=A0 Lacking the former, it isn=E2=80=99t going to j= ust be removed for no reason, and there presently exists no reason to remov= e it.=C2=A0 I cannot predict the future though.=C2=A0 But IME it is exceedi= ngly unlikely to happen.

David J.

--000000000000329a65061be10282--