From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
Cc: | Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Join push-down support for foreign tables |
Date: | 2015-03-04 09:25:39 |
Message-ID: | 54F6CF93.4080701@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015/03/04 17:57, Shigeru Hanada wrote:
> 2015-03-04 17:00 GMT+09:00 Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>:
>> On 2015/03/03 21:34, Shigeru Hanada wrote:
>>> I rebased "join push-down" patch onto Kaigai-san's Custom/Foreign Join
>>> v6 patch.
>>> but still the patch
>>> has an issue about joins underlying UPDATE or DELETE. Now I'm working
>>> on fixing this issue.
>> Is that something like "UPDATE foo ... FROM bar ..." where both foo and bar
>> are remote? If so, I think it'd be better to push such an update down to
>> the remote, as discussed in [2], and I'd like to work on that together!
> A part of it, perhaps. But at the moment I see many issues to solve
> around pushing down complex UPDATE/DELETE. So I once tightened the
> restriction, that joins between foreign tables are pushed down only if
> they are part of SELECT statement. Please see next v4 patch I'll post
> soon.
OK, thanks for the reply!
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Shigeru Hanada | 2015-03-04 09:26:27 | Re: Join push-down support for foreign tables |
Previous Message | David Rowley | 2015-03-04 09:23:29 | Re: Combining Aggregates |