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

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #10847: Connection.setSavepoint()/releaseSavepoint() is not thread-safe
Date: 2014-07-03 21:31:21
Message-ID: 53B5CBA9.70104@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Kirkwood 2014-07-03 22:29:10 Re: Alter system and reload causes bogus complaints about setting changes
Previous Message Greg Stark 2014-07-03 18:54:53 Re: BUG #10847: Connection.setSavepoint()/releaseSavepoint() is not thread-safe