Re: Is SPI safe to use in multi-threaded PL/Java? - Mailing list pgsql-hackers

From MauMau
Subject Re: Is SPI safe to use in multi-threaded PL/Java?
Date
Msg-id 7E4EA2768DA348879F571FE8193A2503@maumau
Whole thread Raw
In response to Re: Is SPI safe to use in multi-threaded PL/Java?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Is SPI safe to use in multi-threaded PL/Java?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
From: "Tom Lane" <tgl@sss.pgh.pa.us>
> "MauMau" <maumau307@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 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 be 100% sure whether there's really no 
problem.

* SPI must not be used in multi-threaded process, even if only one thread 
calls SPI functions at a time.  So what we can say is that PL/Java is not 
safe theoretically in terms of SPI.

Regards
MauMau








pgsql-hackers by date:

Previous
From: Rajeev rastogi
Date:
Subject: Re: COPY table FROM STDIN doesn't show count tag
Next
From: Parul Lakkad
Date:
Subject: Disk usage for intermediate results in join