On Fri, Dec 1, 2017 at 4:01 AM, Antonin Houska wrote:
> I see no other problems here.
Committed, thanks for the report and review.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Jeevan Chalke wrote:
> On Thu, Nov 30, 2017 at 3:44 PM, Jeevan Chalke
> wrote:
>
> On Thu, Nov 30, 2017 at 1:36 AM, Antonin Houska wrote:
>
> The following test
>
> -- Input relation to aggregate push down hook is not safe to pushdown and
> thus
> -- the aggregate cannot be pushed down
On Thu, Nov 30, 2017 at 3:44 PM, Jeevan Chalke <
jeevan.cha...@enterprisedb.com> wrote:
>
>
> On Thu, Nov 30, 2017 at 1:36 AM, Antonin Houska wrote:
>
>> The following test
>>
>> -- Input relation to aggregate push down hook is not safe to pushdown and
>> thus
>> -- the aggregate cannot be pushed
On Thu, Nov 30, 2017 at 1:36 AM, Antonin Houska wrote:
> The following test
>
> -- Input relation to aggregate push down hook is not safe to pushdown and
> thus
> -- the aggregate cannot be pushed down to foreign server.
> explain (verbose, costs off)
> select count(t1.c3) from ft1 t1, ft1 t2 whe
The following test
-- Input relation to aggregate push down hook is not safe to pushdown and thus
-- the aggregate cannot be pushed down to foreign server.
explain (verbose, costs off)
select count(t1.c3) from ft1 t1, ft1 t2 where t1.c1 = postgres_fdw_abs(t1.c2);
produces the following plan
