Re: Push down more UPDATEs/DELETEs in postgres_fdw - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: Push down more UPDATEs/DELETEs in postgres_fdw
Date
Msg-id 1dfb254c-6a25-4bb8-e349-3eefb1f03e64@lab.ntt.co.jp
Whole thread Raw
In response to Re: Push down more UPDATEs/DELETEs in postgres_fdw  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Responses Re: Push down more UPDATEs/DELETEs in postgres_fdw
List pgsql-hackers
On 2016/11/16 13:10, Ashutosh Bapat wrote:
> On Wed, Nov 16, 2016 at 8:25 AM, Etsuro Fujita
> <fujita.etsuro@lab.ntt.co.jp> wrote:
>> On 2016/11/15 19:04, Rushabh Lathia wrote:
>>> Your latest patch doesn't not get apply cleanly apply on master branch.

>> Did you apply the patch set in [1] (postgres-fdw-subquery-support-v4.patch
>> and postgres-fdw-phv-pushdown-v4.patch in this order) before applying the
>> latest patch?

> I don't see any reason why DML/UPDATE pushdown should depend upon
> subquery deparsing or least PHV patch. Combined together they can help
> in more cases, but without those patches, we will be able to push-down
> more stuff. Probably, we should just restrict push-down only for the
> cases when above patches are not needed. That makes reviews easy. Once
> those patches get committed, we may add more functionality depending
> upon the status of this patch. Does that make sense?

OK, I'll extract from the patch the minimal part that wouldn't depend on 
the two patches.

Best regards,
Etsuro Fujita





pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Document how to set up TAP tests for Perl 5.8.8
Next
From: Yury Zhuravlev
Date:
Subject: Re: WIP: About CMake v2