| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Shigeru Hanada *EXTERN* <shigeru(dot)hanada(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Optimization for updating foreign tables in Postgres FDW |
| Date: | 2014-08-28 11:40:41 |
| Message-ID: | 53FF1539.8050904@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(2014/08/27 23:05), Tom Lane wrote:
> I wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> Hmm, I'm worried that may be an API contract violation.
> Actually, there's another problem there. What of UPDATE or DELETE with a
> LIMIT clause, which is something that seems to be coming down the pike:
> https://commitfest.postgresql.org/action/patch_view?id=1550
I'd like to try to extend the functionality so as to push
UPDATE/DELETE-with-LIMIT down into the remote server if it's safe. But
I don't yet know if it's possible, because I started looking into the
UPDATE/DELETE-with-LIMIT patch just now ...
Thanks,
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2014-08-28 11:46:57 | Re: psql \watch versus \timing |
| Previous Message | Andres Freund | 2014-08-28 11:20:07 | Re: [Fwd: Re: proposal: new long psql parameter --on-error-stop] |