| From: | Amine Tengilimoglu <aminetengilimoglu(at)gmail(dot)com> |
|---|---|
| To: | "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: | what is the best way to access cold data on another server? |
| Date: | 2020-05-13 07:12:47 |
| Message-ID: | CADTdw-yP_n1zDWPzNhBMe4z2siSoeU9rX4M7DLZCbtJfs1ThDQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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..
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Holger Jakobs | 2020-05-13 07:24:41 | Re: what is the best way to access cold data on another server? |
| Previous Message | Scott Ribe | 2020-05-10 15:03:41 | Re: Deactivate/disable User id in Postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Holger Jakobs | 2020-05-13 07:24:41 | Re: what is the best way to access cold data on another server? |
| Previous Message | Matthias Apitz | 2020-05-13 05:34:05 | Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction |