| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
| Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql_fdw, FDW for PostgreSQL server |
| Date: | 2012-03-05 21:19:40 |
| Message-ID: | 13096.1330982380@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> I'm inclined to think that if we provide this function in core at all,
> it should take a parameter list long enough to let it fill in the Path
> completely. That would imply that any future changes in Path structs
> would result in a change in the parameter list, which would break
> callers --- but it would break them in an obvious way that the C
> compiler would complain about. If we leave it as-is, those same callers
> would be broken silently, because they'd just be failing to fill in
> the new Path fields.
I've committed the PlanForeignScan API change, with that change and
some other minor editorialization. The pgsql_fdw patch now needs an
update, so I set it back to Waiting On Author state.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Artur Litwinowicz | 2012-03-05 21:32:44 | Re: elegant and effective way for running jobs inside a database |
| Previous Message | Robert Haas | 2012-03-05 21:17:01 | Re: Command Triggers, patch v11 |