On Tue, Oct 25, 2011 at 14:08, Tom Lane <t...@sss.pgh.pa.us> wrote: > Magnus Hagander <mag...@hagander.net> writes: >> 2011/10/25 Shigeru Hanada <shigeru.han...@gmail.com>: >>> I'd like to propose pgsql_fdw, FDW for external PostgreSQL server, as a >>> contrib module. I think that this module would be the basis of further >>> SQL/MED development for core, e.g. join-push-down and ANALYZE support. > >> I have not looked at the code itself, but I wonder if we shouldn't >> consider making this a part of core-proper, not just a contrib module. >> The fact that it isn't *already* available in core surprises a lot of >> people... > > We've just spent a whole lot of blood and sweat on making the extension > mechanism work nicely. I don't understand this urge to not use it.
We're back to the old discussion, I guess.. I'm happy to see it as an extension, but I think it should be included with the standard installation. Like we do with for example pl/pgsql (which I realize has a dependency on the backend anyway, so it can't be done another way easily) and pl/perl (which doesn't, AFAIK, so it's a better example) > 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 :) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers