Hi
> The issue here is an architectural mismatch between PostgreSQL and > the JVM, made worse by the user's very stored-proc-heavy code. Some > other runtime that's designed to co-operate with a multiprocessing > environment could well be fine, but the JVM isn't. At least, the > Sun/Oracle/OpenJDK JVM isn't. Actually the lack of threads make any vm quite limit in some aspects of scalability. The desire to use jvm is the result that there is no desire to reinvent the wheel. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
