Hello Oliver,
This is a problem with a full receive buffer on the client side blocking
the server from writing more results while the client tries to send more
commands to server. Either split your server input into several single
statements or increase the receive buffer size of your client.
Daniel Migowski
PS: I'd like this problem to be solved, too, but this would need either
a multithreaded driver, or some timeout handling within the driver, both
coming with some small performance losses. Maybe an option should be
added to the driver here...
Oliver Hitz schrieb:
> On 28 Apr 2009, Oliver Hitz wrote:
>
>> Anything else that I could try? I will try if loglevel=2 results in some
>> useful output now.
>>
>
> Ok now here's a query that hangs after it has been sent. Right after
> "Sync" the program hangs:
>
> 19:24:45.594 (172) simple execute,
handler=org.postgresql.jdbc2.AbstractJdbc2Statement$StatementResultHandler@d7e2b57,maxRows=0, fetchSize=0, flags=17
> 19:24:45.594 (172) FE=> Parse(stmt=null,query="SELECT changes.what,changes.whenchanged FROM changes WHERE what=$1
ANDwhenchanged>$2",oids={1043,0})
> 19:24:45.594 (172) FE=> Bind(stmt=null,portal=null,$1=<'docsiscmts'>,$2=<'2009-04-28 13:41:32.425000 +02:00:00'>)
> 19:24:45.594 (172) FE=> Describe(portal=null)
> 19:24:45.594 (172) FE=> Execute(portal=null,limit=0)
> 19:24:45.594 (172) FE=> Sync
>
> Nothing special on the backend. From what I can see, all processes are in
> idle state.
>
> Any idea what could be wrong here?
>
> Thanks in advance,
>
> Oliver
>
