John R Pierce <pierce@xxxxxxxxxxxx> writes: > On 9/17/2014 5:02 PM, cowwoc wrote: >> This shouldn't be too technically difficult to pull off. > right. > wait, which user? the java user/developer who typically hasn't a > clue how system-level stuff functions or operates, or the postgresql > database administrator, who probably hasn't a clue how java works > internally ? There are a number of reasons why this (pl/java in core) isn't likely to happen; one being that I think a good fraction of the core PG developers fall into the "haven't a clue how java works internally" camp. But here's the *key* reason: if pl/java is failing to stay afloat as an external project, that is a terrible reason for pulling it into core. It suggests strongly that the manpower or interest to keep it going simply doesn't exist. Making it part of the core distribution would not fix that, and moreover it would demand attention from PG core developers who are not particularly motivated or capable to do anything with it. If you feel that pl/java isn't sufficiently well maintained, the short answer is that you should get involved with it as it is. In the end, open source is all about "scratch your own itch". regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
