"Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx> writes: > One more thought -- I keep coming back to the fact that when we turn > on logging in the JDBC driver on the client side, the problem does not > occur. The only possible reason I can see for this having any affect > on the problem is the small delay introduced by the synchronous > logging. Since this is only showing up on commit of a database > transaction which follows close on the heels of a rollback on the same > connection, is there any chance that there is some very small > "settling time" needed for a rollback, and we're sometimes getting in > ahead of this? (1) No. (2) Even if we posit the existence of such a serious bug as that, it wouldn't explain how control gets to the SIGINT response code. regards, tom lane
