| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Archiving Data to Another DB? |
| Date: | 2018-04-11 18:33:53 |
| Message-ID: | CAHJZqBDCoWa5Hj9Ue282_tgW1YR+2AP7enfJhH99CRJD29h-sw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 11, 2018 at 1:13 PM, Don Seiler <don(at)seiler(dot)us> wrote:
>
> I had considered this as well, as this would allow me to rollback the
> delete (assuming my intel on postgres_fdw transactions was correct, which
> it may not be after all). I wondered if a remote insert would be broken up
> into individual inserts like the remote delete was, as that would be
> equally unappealing for the same reasons. But obviously worth confirming.
>
I have now confirmed that a remote INSERT does get broken up into a single
INSERT for each row.
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Seiler | 2018-04-11 18:38:39 | Re: Archiving Data to Another DB? |
| Previous Message | Adrian Klaver | 2018-04-11 18:33:46 | Re: Archiving Data to Another DB? |