From: | "James Im" <im-james(at)hotmail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: SQL query never ends |
Date: | 2006-08-13 06:18:41 |
Message-ID: | BAY7-F21FF57C04C5A9BD222C47E96490@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
>>I think that one way to find out would be to get enough information
>>about what's happening from the java side (something like loglevel=10
>>?). The driver (or a special version of the driver just for this
>>purpose) could contain a lot more traces so that: 1) any problem of
>>synchronization could be discarded. 2) you could know what java has sent
>>through the socket and 3) what it has received until the moment the
>>code will block.
>
>This is essentially what loglevel=2 already does already ..
>
I don't know.
I've been asked a few times if my app had synchronization problems. If
the driver traces contained enough info then these questions were
superfluous I guess.
If you knew precisely what network traffic was going in and out through
the socket why had I to capture the network traffic with wireshark and co?
Anyhow. You know better than me.
_________________________________________________________________
Find dine dokumenter lettere med MSN Toolbar med Windows-pc-sgning:
http://toolbar.msn.dk
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2006-08-13 10:56:29 | Re: SQL query never ends |
Previous Message | Oliver Jowett | 2006-08-13 05:36:51 | Re: SQL query never ends |