| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, SAKAMOTO Masahiko <sakamoto(dot)masahiko(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: patch: SQL/MED(FDW) DDL |
| Date: | 2010-09-24 12:13:54 |
| Message-ID: | AANLkTimcSrQk_bgAa0LSUxZzuWLJ39cmAnMsM6o99Kb0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 24, 2010 at 5:56 AM, Itagaki Takahiro
<itagaki(dot)takahiro(at)gmail(dot)com> wrote:
> I think there are two type of FDWs. One is a simple flat file wrapper
> used by COPY FROM now, that doesn't require any planner hooks.
> Another is a connector to an external database, like as dblink, that
> should be integrated with the planner.
This is a good point. On the one hand, I do agree that the API for
simple things like processing CSV files shouldn't be overly complex.
So perhaps we could start with a simple API and extend it later. On
the other hand, understanding how some of the more complex cases ought
to work provides insight into handling the simpler cases. So I think
we should aim to have at least a sketch of a design for the whole
feature, and then if in phase 1 we want to implement only the easier
parts, that's OK.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-09-24 12:17:41 | Re: Enable logging requires restart |
| Previous Message | Robert Haas | 2010-09-24 12:05:59 | Re: patch: SQL/MED(FDW) DDL |