On Wed, Mar 9, 2016 at 9:22 PM, Robert Haas wrote:
> On Wed, Mar 9, 2016 at 2:23 AM, Ashutosh Bapat
> wrote:
> > [ new patch ]
>
> This looks OK to me. Committed!
>
>
Thanks.
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
On Wed, Mar 9, 2016 at 2:23 AM, Ashutosh Bapat
wrote:
> [ new patch ]
This looks OK to me. Committed!
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subs
> This patch needs to be rebased.
>
>
Done.
> + /*
> +* TODO: we should worry about EPQ path but should
> that path have
> +* pathkeys? I guess, that's not really important
> since it's just
> +* going to evaluate the join from whole-r
On Tue, Feb 23, 2016 at 7:48 AM, Ashutosh Bapat
wrote:
> Rushabh pointed out that declarations of helper functions
> get_useful_ecs_for_relation and get_useful_pathkeys_for_relation() are part
> of FDW routines declarations rather than helper function declaration. Since
> those functions are relat
Rushabh pointed out that declarations of helper functions
get_useful_ecs_for_relation and get_useful_pathkeys_for_relation() are part
of FDW routines declarations rather than helper function declaration. Since
those functions are related to this patch, the attached patch moves those
declaration in
Hi All,
Now that we have join pushdown support in postgres_fdw, we can leverage the
sort pushdown mechanism for base relations to work for pushed down joins as
well. PFA patch for the same.
The code to find useful set of pathkeys and then generate paths for each
list of pathkeys is moved into a fu