Postgres Pro
Downloads
Home   >   mailing lists

Re: LOCK TABLE oddness in PLpgSQL function called via JDBC - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: LOCK TABLE oddness in PLpgSQL function called via JDBC
Date
Msg-id 19396.1002057772@sss.pgh.pa.us
Whole thread Raw
In response to LOCK TABLE oddness in PLpgSQL function called via JDBC  (Dave Harkness <daveh@MEconomy.com>)
Responses Re: LOCK TABLE oddness in PLpgSQL function called via  (Dave Harkness <daveh@MEconomy.com>)
List pgsql-jdbc
Tree view 
Dave Harkness <daveh@MEconomy.com> writes:
> The problem I'm seeing is that two database transactions,
> initiated via JDBC, are able to obtain simultaneous exclusive table locks
> on the same table.

Sounds to me like JDBC is feeding all your commands through a single
database connection, which means that what you think are independent
transactions are really not.  Better take a closer look at what you're
doing.

            regards, tom lane

pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: driver fails to handle strings in query statements properly
Next
From: David Siebert
Date:
Subject: Re: TIMESTAMP