From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dhritman Roy <dhritman.roy@NetCracker.com>
cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: dblink Future support vs FDW
In-reply-to: <609c8cd402e145e2af12bcfe20ac22e1@NetCracker.com>
References: <609c8cd402e145e2af12bcfe20ac22e1@NetCracker.com>
Comments: In-reply-to Dhritman Roy <dhritman.roy@NetCracker.com>
	message dated "Thu, 27 Jun 2024 15:32:13 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1747821.1719504012.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 27 Jun 2024 12:00:12 -0400
Message-ID: <1747822.1719504012@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1747822.1719504012%40sss.pgh.pa.us>
Precedence: bulk

Dhritman Roy <dhritman.roy@NetCracker.com> writes:
> My organization is building something which is using dblink and what we =
are building shall take several months and then to be offered to a client.
> I just wanted to check what is the future/roadmap of dblink?
> Is it going to be obsolete/removed from PostGreSQL in upcoming versions?

I don't foresee us removing it any time soon, because there are things
you can do with it that aren't possible in the FDW model
(particularly, issue DDL to the remote server).  Even if we did kick
it out of the core distribution at some point, it could live on as an
externally-maintained extension.

Having said that, it is a bit of a development backwater, so you
should probably not count on anyone being interested enough to add
new features to it.

			regards, tom lane