From: Tom Lane t...@sss.pgh.pa.us
That, more or less. There is exactly zero provision in the Postgres
code for multiple threads to exist inside a backend process. It's
possible that PL/Java manages to completely insulate the Java world
from the C world, so that the C code never sees more than
From: Tom Lane t...@sss.pgh.pa.us
MauMau maumau...@gmail.com writes:
To put the question in other words, is it safe to load a multi-threaded
PL
library in the single-threaded backend process, if the PL only calls SPI
in
the main thread?
When it breaks, we're not going to be concerned.
I
MauMau maumau...@gmail.com writes:
From: Tom Lane t...@sss.pgh.pa.us
When it breaks, we're not going to be concerned.
I may not understand your nuance. Which of the following do you mean?
* PL/Java's design is dangerous in terms of the mixture of single- and
multi-threading, and we cannot
MauMau maumau...@gmail.com writes:
Is PL/Java safe to use in terms of its threading design? I'm going to ask
the PL/Java community about this too, but I'd ask for opinions here because
I believe people in this community have seasoned knowledge of OS and SPI.
To put the question in other
