Re: BUG #10847: Connection.setSavepoint()/releaseSavepoint() is not thread-safe - Mailing list pgsql-bugs

From John R Pierce
Subject Re: BUG #10847: Connection.setSavepoint()/releaseSavepoint() is not thread-safe
Date
Msg-id 53B5CBA9.70104@hogranch.com
Whole thread Raw
In response to Re: BUG #10847: Connection.setSavepoint()/releaseSavepoint() is not thread-safe  (Greg Stark <stark@mit.edu>)
List pgsql-bugs
On 7/3/2014 11:54 AM, Greg Stark wrote:
> I think you need to report this to the JDBC mailing list at
> pgsql-jdbc@postgresql.org
>
> http://www.postgresql.org/list/pgsql-jdbc/
>
> The Postgres libpq interface is most definitely not threadsafe but I
> don't see any indication in that stack trace that it's using libpq. It
> seems to be pure Java there.

yes, the jdbc driver is pure java.  you still should avoid using a jdbc
sql connection from more than one thread on the same transaction.  its
fine to reuse a connection between transactions as long as only one
thread is using it at a time.



--
john r pierce                                      37N 122W
somewhere on the middle of the left coast

pgsql-bugs by date:

Previous
From: Greg Stark
Date:
Subject: Re: BUG #10847: Connection.setSavepoint()/releaseSavepoint() is not thread-safe
Next
From: Mark Kirkwood
Date:
Subject: Re: Alter system and reload causes bogus complaints about setting changes