| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
| Subject: | Re: pgsql_fdw, FDW for PostgreSQL server |
| Date: | 2012-03-10 16:38:51 |
| Message-ID: | 22362.1331397531@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> writes:
> Thanks for the review. Agreed to write own depraser for pgsql_fdw
> which handles nodes which can be pushed down. Every SQL-based FDW
> which constructs SQL statement for each local query would need such
> module inside.
Yeah. That's kind of annoying, and the first thing you think of is that
we ought to find a way to share that code somehow. But I think it's
folly to try to design a shared implementation until we have some
concrete implementations to compare. An Oracle FDW, for instance, would
need to emit SQL code with many differences in detail from pgsql_fdw.
It's not clear to me whether a shared implementation is even practical,
but for sure I don't want to try to build it before we've done some
prototype single-purpose implementations.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marti Raudsepp | 2012-03-10 17:00:37 | Re: Caching for stable expressions with constant arguments v6 |
| Previous Message | Tom Lane | 2012-03-10 16:34:33 | Re: pgsql_fdw, FDW for PostgreSQL server |