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

Re: executeUpdate() deadlock

From: Fischer Krisztián <fischer(at)borganization(dot)com>
To: pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>
Cc: Waldomiro <wmiro(at)ig(dot)com(dot)br>
Subject: Re: executeUpdate() deadlock
Date: 2004-01-26 13:19:31
Message-ID: 401513E3.8090800@borganization.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
I see... I have to handle such cases by myself (for example to detect 
software problems).

Thanks wmiro!

Waldomiro wrote:
> I've done this test on a psql program, so the second session waited up to
> the first session be committed.
> Postgres doesn't throw an exception because he manages the concurrency.
> wmiro.

-- 
Fischer Krisztián <fischer(at)borganization(dot)com>
Tel: (+36)70/3843835, (+36)1/3360547
Borganization Kft.


In response to

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2004-01-26 13:40:56
Subject: Re: OutOfMemoryError - bug or human error?
Previous:From: WaldomiroDate: 2004-01-26 12:39:43
Subject: Re: executeUpdate() deadlock

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