>> ATM I'm not sure it's even a good idea to push pgsql_fdw into contrib. >> Once we do that its release schedule will get locked to core's --- >> wouldn't it be better to keep flexibility for now, while it's in such >> active development? > > I would be happy to keep it outside, and integrate it in the final CF > for example :) > Right now, file_fdw is the only FDW module that we have in the core, however, it is inadequacy to proof the new concept of FDW feature to utilize external RDBMS, such as join push-down of foreign tables.
I think the pgsql-fdw module also should be included in the core distribution as a basis of future enhancement, unless we don't need any working modules when an enhancement of FDW is proposed. Thanks, -- KaiGai Kohei <kai...@kaigai.gr.jp> -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers