dblink Future support vs FDW
Hello,
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.
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 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 not want to end up in a situation where we develop something in few months and then we find that the PostGreSQL support is ending with a new version.
Any information/pointers related to future of dblink will be very useful for us and highly appreciated.
Regards
ROY.
________________________________
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
On Thursday, June 27, 2024, Dhritman Roy <dhritman.roy@netcracker.com>
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 and
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 not
want to end up in a situation where we develop something in few months and
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’t 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.
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
On 6/27/24 08:32, Dhritman Roy wrote:
Hello,
This is my attempt to seek support at PostGreSQL.
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 not want to end up in a situation where we develop something in few
months and then we find that the PostGreSQL support is ending with a new
version.
I would say that is highly unlikely. Even if it where to happen at some
point in the distant future you still have:
Open source code under a permissive license that you could keep running
with.
Any information/pointers related to future of dblink will be very useful
for us and highly appreciated.Regards
ROY.
------------------------------------------------------------------------
The information transmitted herein is intended only for the person or
entity to which it is addressed and may contain confidential,
proprietary and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.
--
Adrian Klaver
adrian.klaver@aklaver.com