| From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
|---|---|
| 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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thom(at)linux(dot)com>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |
| Date: | 2015-03-25 09:53:27 |
| Message-ID: | CAFjFpRcw2pD36HVRYTWft_dCRVj67FJL=rJbbVfprjQBd5BkSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 25, 2015 at 3:14 PM, Shigeru HANADA <shigeru(dot)hanada(at)gmail(dot)com>
wrote:
>
> Or bottom of make_join_rel(). IMO build_join_rel() is responsible for
> just building (or searching from a list) a RelOptInfo for given relids.
> After that make_join_rel() calls add_paths_to_joinrel() with appropriate
> arguments per join type to generate actual Paths implements the join.
> make_join_rel() is called only once for particular relid combination, and
> there SpecialJoinInfo and restrictlist (conditions specified in JOIN-ON and
> WHERE), so it seems promising for FDW cases.
>
I like that idea, but I think we will have complex hook signature, it won't
remain as simple as hook (root, joinrel).
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2015-03-25 10:09:42 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |
| Previous Message | Shigeru HANADA | 2015-03-25 09:44:39 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |