Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock

Поиск
Список
Период
Сортировка
От Shawn Chasse
Тема Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock
Дата
Msg-id 1b81b11d0811111134y67a0b797k23ce4279b9665e13@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock  (Kris Jurka <books@ejurka.com>)
Список pgsql-jdbc
I believe so, This is a simple operation that should be fairly straightforward and typically happens hundreds of times per day. When this occurs, i have waited hours without it ever returning.

checking the system this is running on, cpu usage etc are all nil from my process that is working on this.

On Tue, Nov 11, 2008 at 2:26 PM, Kris Jurka <books@ejurka.com> wrote:


On Tue, 11 Nov 2008, Shawn Chasse wrote:

Re Kris large parameter count: How many would be considered large? The table
that always seems to be the one getting the inserts when this occurs is
defined as follows:

Oliver is correct, the deadlock I was referring to would show different symptoms, so this isn't it.  In this case you are likely looking at some kind of a server problem.  Are you sure you're truly deadlocked, not just waiting on something (check pg_locks)?

Kris Jurka

В списке pgsql-jdbc по дате отправления:

Предыдущее
От: Kris Jurka
Дата:
Сообщение: Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock
Следующее
От: Magnus Hagander
Дата:
Сообщение: JDBC and certificates