From: | Marcin Waldowski <M(dot)Waldowski(at)sulechow(dot)net> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Locking on PGStream.ReceiveChar(PGStream.java:256) |
Date: | 2006-12-01 21:55:33 |
Message-ID: | 4570A4D5.4000707@sulechow.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
I don't know a protocol yet, but perhaps it is possible to detect such
problem with PostgreSQL database and throw SQLException. In this way
stablity of Postgresql jdbc driver will be independent from stability of
PostgreSQL (jdbc will not hang). If you tell me that it is possible and
worth doing then I will try to find a solution and make a patch.
Marcin Waldowski
Kris Jurka wrote:
>
>
> On Fri, 1 Dec 2006, Marcin Waldowski wrote:
>
>> Hello.
>>
>> JDBC version: 8.1-407 JDBC 3 PostgreSQL version: 8.1.5-1 for Windows
>> Database encoding: UTF8
>>
>> I observed a lock at at
>> org.postgresql.core.PGStream.ReceiveChar(PGStream.java:256)
>>
>> It happens after about hour of our perfomance test (high workload -
>> 50 threads are executing various short operations on database)
>>
>> What can I do to avoid this problem?
>>
>
> This sort of problem has been attributed to the windows port of
> postgresql. This thread here resulted in a fix that will be included
> in the 8.1.6 release and may fix the problem.
>
> http://archives.postgresql.org/pgsql-hackers/2006-10/thrd7.php#00289
>
> Kris Jurka
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2006-12-01 23:20:00 | Re: Locking on PGStream.ReceiveChar(PGStream.java:256) |
Previous Message | Marcin Waldowski | 2006-12-01 21:37:47 | Re: Locking on PGStream.ReceiveChar(PGStream.java:256) |