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

From: Greg Stark <stark(at)mit(dot)edu>
To: christian(at)schlichtherle(dot)de
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #10847: Connection.setSavepoint()/releaseSavepoint() is not thread-safe
Date: 2014-07-03 18:54:53
Message-ID: CAM-w4HMPA9JVNzuMQuVMoN3yK7cEd8jGpkAOMXmD5DcusjBAcg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2014-07-03 21:31:21 Re: BUG #10847: Connection.setSavepoint()/releaseSavepoint() is not thread-safe
Previous Message Amit Kapila 2014-07-03 16:57:01 Re: Alter system and reload causes bogus complaints about setting changes