| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Holger Jakobs <holger(at)jakobs(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: what is the best way to access cold data on another server? |
| Date: | 2020-05-14 15:26:11 |
| Message-ID: | CAMkU=1wkqYx8DhhovYECyBE-ZtPfBPyekX_vd=XciT_qp__uAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Wed, May 13, 2020 at 3:24 AM Holger Jakobs <holger(at)jakobs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ankush Chawla | 2020-05-14 15:32:47 | Postgres Upgrades could not open version file PG_VERSIOn |
| Previous Message | Wim Bertels | 2020-05-14 14:50:28 | Re: viewing connectioninfo used by subscriber on the publication server when inactive |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eduard Rozenberg | 2020-05-14 15:35:56 | vacuumdb --jobs deadlock: how to avoid pg_catalog ? |
| Previous Message | Support | 2020-05-14 13:41:14 | Re: Reuse an existing slot with a new initdb |