On Wed, Sep 17, 2014 at 11:42 PM, cowwoc <cowwoc@xxxxxxxxxxxxxxxx> wrote: > Tom, > > For starters, let's talk strictly about improving the deployment situation, > which the core team *is* uniquely positioned to do. > > The pl/java author(s) should figure out what needs to be done but once > that's known we need to do *something* in core so the deployment process is > reduced to 1-2 steps max (CREATE EXTENSION pljava, and add Java to > Postgresql's library path) You've got it exactly backwards. 'core' should include as little as possible. In fact, many things that are in contrib (for example passwordcheck) today are holdovers from when standards of acceptance to contrib were lower. Rather than throwing the kitchen sink into core, IMSNO i would be a much better investment to spend efforts on expanding 'CREATE EXTENSION' so that it could do things like connect to internet repositories and install precomplied libraries. In lieu of that, if you wanted to make pl/java more accessible the first place I'd suggest going to the repository maintainers like pgdg and doing everything possible to help them get pl/java building and packaged. merlin -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
