Re: LOCK TABLE oddness in PLpgSQL function called via JDBC

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: LOCK TABLE oddness in PLpgSQL function called via JDBC
Дата
Msg-id 19396.1002057772@sss.pgh.pa.us
обсуждение исходный текст
Ответ на LOCK TABLE oddness in PLpgSQL function called via JDBC  (Dave Harkness <daveh@MEconomy.com>)
Ответы Re: LOCK TABLE oddness in PLpgSQL function called via
Список pgsql-jdbc
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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: driver fails to handle strings in query statements properly
Следующее
От: David Siebert
Дата:
Сообщение: Re: TIMESTAMP