| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Amine Tengilimoglu <aminetengilimoglu(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: what is the best way to access cold data on another server? |
| Date: | 2020-05-13 11:35:06 |
| Message-ID: | 4871eb5b1c5127c3c0113cc0da889b93c29afc9b.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wim Bertels | 2020-05-14 10:50:42 | viewing connectioninfo used by subscriber on the publication server when inactive |
| Previous Message | Amine Tengilimoglu | 2020-05-13 07:34:35 | Re: what is the best way to access cold data on another server? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Support | 2020-05-13 13:18:38 | Re: Reuse an existing slot with a new initdb |
| Previous Message | Tom Ellis | 2020-05-13 11:02:51 | Why is it that “aggregate functions are not allowed in FROM clause of their own query level”? |