Обсуждение: Re: what is the best way to access cold data on another server?
dblink is outdated, postgres_fdw is current. Am 13.05.20 um 09:12 schrieb Amine Tengilimoglu: > Hello everyone; > > In addition to the actively used data, there are other data that > are very little accessed. I want to separate the less used data to > save space and reduce maintenance operations. I want to use a separate > postgres instance for this. Now the question is; How do I link these > two instances? postgres_fdw or dblink? or what other solution? Which > one would be better? > > > > thanks in advance.. -- Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
I am concerned about the security of fdw. so I actually asked for its comparison with dblink and wondered if there was any other technique to do this.
Holger Jakobs <holger@jakobs.com>, 13 May 2020 Çar, 10:24 tarihinde şunu yazdı:
dblink is outdated, postgres_fdw is current.
Am 13.05.20 um 09:12 schrieb Amine Tengilimoglu:
> Hello everyone;
>
> In addition to the actively used data, there are other data that
> are very little accessed. I want to separate the less used data to
> save space and reduce maintenance operations. I want to use a separate
> postgres instance for this. Now the question is; How do I link these
> two instances? postgres_fdw or dblink? or what other solution? Which
> one would be better?
>
>
>
> thanks in advance..
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
On Wed, May 13, 2020 at 3:24 AM Holger Jakobs <holger@jakobs.com> wrote:
dblink is outdated, postgres_fdw is current.
dblink may not be getting lots of improvements, but it is maintained to the same standards as postgres_fdw is. FDW inhibits parallel queries, on both sides. dblink maintains that possibility, (while tedious to do in a useful way). Also, FDW cannot push UDF calls, while dblink can if you manually write them into the sent query.
Cheers,
Jeff