| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "vinu" <vinu(dot)rm(at)gmail(dot)com>,<pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Locking |
| Date: | 2012-04-05 17:57:40 |
| Message-ID: | 4F7D96C40200002500046BFF@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
vinu <vinu(dot)rm(at)gmail(dot)com> wrote:
> I am having the same issue.
For the benefit of those who don't remember the post:
http://archives.postgresql.org/pgsql-jdbc/2008-04/msg00094.php
> Unless we close the connection or do a connection.commit(), the
> AccessShareLock is not getting released. ResultSet.close() and
> PreparedStatement.close() is not having any effect on this
> behavior. Is this the expected behavior ?
Yes. Did you look at the existing reply?
http://archives.postgresql.org/pgsql-jdbc/2008-04/msg00095.php
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | BCH | 2012-04-06 08:05:54 | JDBC DatabaseMetaData problem |
| Previous Message | cognizant | 2012-04-05 14:58:40 | Issues with IN-OUT parameters for Array of Objects in EDB using Java |