2010/9/15 Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>:
> The API needs to be simple and version-independent, so that you can
> write simple wrappers like the flat file wrapper easily. At the same
> time, it needs to be very flexible, so that it allows safely pushing
> down all kinds constructs like functions, aggregates and joins. The
> planner needs to know which constructs the wrapper can handle and get
> cost estimates for the foreign scans. Those two goals are at odds.
The patch didn't say nothing about the API design, no?
It just implement FOREIGN TABLE commands in the SQL standard,
and we need the part anyway if we want to support the standard.
--
Itagaki Takahiro