Re: Deadlock detection

Kris Jurka wrote:
> 
> 
> On Thu, 22 Jan 2009, Oliver Jowett wrote:
> 
>> Oliver Jowett wrote:
>>
>> This passes the regression testsuite with antiDeadlock=true, but I don't
>> have a deadlock testcase on hand to try unfortunately.
>>
> 
> This has a test case which deadlocks consistently:
> 
> http://archives.postgresql.org/pgsql-jdbc/2008-10/msg00045.php

Perfect, thanks

My changes seem to pass BatchDeadLock with antiDeadlock=true (and still
hang with antiDeadlock=false):

> 14:59:45.233 (1)  FE=> Execute(portal=null,limit=1)
> 14:59:45.233 (1)  FE=> Sync
> Warning: possible socket deadlock detected (timeout=30000, remaining buffer=1299975
> java.lang.Throwable: Deadlock call stack
> 	at org.postgresql.core.AntiDeadlockStream.flush(AntiDeadlockStream.java:83)
> 	at org.postgresql.core.PGStream.flush(PGStream.java:517)
> 	at org.postgresql.core.v3.QueryExecutorImpl.sendSync(QueryExecutorImpl.java:692)
> 	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:342)
> 	at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2693)
> 	at BatchDeadLock.main(BatchDeadLock.java:40)
> 15:00:15.234 (1)  <=BE ParseComplete [S_1]
> 15:00:15.234 (1)  <=BE ParameterDescription
> 15:00:15.235 (1)  <=BE NoData
> 15:00:15.235 (1)  <=BE BindComplete [null]
> 15:00:15.235 (1)  <=BE CommandStatus(INSERT 0 1)
> 15:00:15.235 (1)  <=BE ParseComplete [S_2]
> 15:00:15.235 (1)  <=BE ParameterDescription
> 15:00:15.235 (1)  <=BE NoData
> [.. etc ..]

-O