what is the best way to access cold data on another server?

Started by Amine Tengilimoglualmost 6 years ago5 messagesgeneral
Jump to latest
#1Amine Tengilimoglu
aminetengilimoglu@gmail.com

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..

#2Holger Jakobs
holger@jakobs.com
In reply to: Amine Tengilimoglu (#1)
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

#3Amine Tengilimoglu
aminetengilimoglu@gmail.com
In reply to: Holger Jakobs (#2)
Re: what is the best way to access cold data on another server?

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ı:

Show quoted text

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

#4Laurenz Albe
laurenz.albe@cybertec.at
In reply to: Amine Tengilimoglu (#1)
Re: what is the best way to access cold data on another server?

On Wed, 2020-05-13 at 10:12 +0300, Amine Tengilimoglu wrote:

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?

Foreign Data Wrapper is a good option, and yes, it is secure.

Another option would be to store these data as CSV files and use file_fdw
to define them as "external tables".

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

#5Jeff Janes
jeff.janes@gmail.com
In reply to: Holger Jakobs (#2)
Re: what is the best way to access cold data on another server?

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