Skip site navigation (1) Skip section navigation (2)

Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock

From: "Shawn Chasse" <shawnchasse(at)gmail(dot)com>
To: "Kris Jurka" <books(at)ejurka(dot)com>
Cc: "Oliver Jowett" <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock
Date: 2008-11-11 19:34:12
Message-ID: 1b81b11d0811111134y67a0b797k23ce4279b9665e13@mail.gmail.com (view raw or flat)
Thread:
Lists: 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(at)ejurka(dot)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
>

In response to

pgsql-jdbc by date

Next:From: Magnus HaganderDate: 2008-11-13 12:38:29
Subject: JDBC and certificates
Previous:From: Kris JurkaDate: 2008-11-11 19:26:31
Subject: Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group