Re: postgres_fdw insert extremely slow

From: pabloa98 <pabloa98(at)gmail(dot)com>
To: Mats Julian Olsen <mats(at)duneanalytics(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, wilhelm(at)duneanalytics(dot)com
Subject: Re: postgres_fdw insert extremely slow
Date: 2020-11-27 21:00:20
Message-ID: CAEjudX6v_cAC1GeLWpboOq5KWsBXx-VNP2y4wvp8OuodHE0czg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I would like to suggest for postgres_fdw: If the foreign database is
PostgreSQL, the link should just pass through all the CRUD SQL commands to
the other database.

If the other database is of a version so different that cannot make sense
of the CRUD SQL command, it will generate an error and that's it.

This would be very useful to keep datasets synchronized.

Pablo

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2020-11-27 21:25:25 Re: postgres_fdw insert extremely slow
Previous Message Tom Lane 2020-11-27 17:37:45 Re: SV: Problem with pg_notify / listen