Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)
| От | Michael Paquier |
|---|---|
| Тема | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |
| Дата | |
| Msg-id | CAB7nPqQXTA-B3Qzg8K2b7uLYTAkkBSO8=Uffx0T51xXmBa-bog@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) (Michael Paquier <michael.paquier@gmail.com>) |
| Ответы |
Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)
|
| Список | pgsql-hackers |
On Fri, Feb 13, 2015 at 6:12 PM, Michael Paquier <michael.paquier@gmail.com> wrote:
-- On Fri, Feb 13, 2015 at 4:59 PM, Kouhei Kaigai <kaigai@ak.jp.nec.com> wrote:> Where are we on this? AFAIK, we have now a feature with no documentation
> and no example in-core to test those custom routine APIs, hence moved to
> next CF.
>
Now Hanada-san is working on the example module that use this new
infrastructure on top of postgres_fdw. Probably, he will submit the
patch within a couple of days, for the upcoming commit fest.I am a bit surprised by that. Are you planning to give up on the ctidscan module module and
Sorry I typed the wrong key.
So... Are you planning to give up on the ctidscan module and submit only the module written by Hanada-san on top of postgres_fdw? As I imagine that the goal is just to have a test module to run the APIs why would the module submitted by Hanada-san be that necessary?
Michael
В списке pgsql-hackers по дате отправления: