Dave Page a écrit :
>> From: Ludek Finstrle [mailto:luf@pzkagis.cz]
>> It seems to me I have to kick Dave to take a look at this :-)
>> Dave is pgAdmin developer so he could give a light on the problem.
>>
>> Dave: Could you take a look at this problem?
>
> Arnaud,
>
> When you are testing, please make sure that the psqlODBC's mylog and
> commlog are switched off, and that SQL Tracing is turned off in the ODBC
> control panel applet.
>
> Also, please note that pgAdmin has very lightweight data access classes
> written over libpq - much more lightweight than the ODBC driver. Most of
> the overhead in pgAdmin comes from rendering the data in the grid
> control.
>
> Regards, Dave.
Dave,
All logging is off when I run tests. I only turned them on on
Ludek's request for debugging purposes. Tracing is always off in
the ODBC pannel.
What looks strange to me is that while the query is running
(during the "open" method of the recordset), processor usage is 0%
on the server and the workstation. Network usage is very low :
~50kB on a 100Mbps connection, during the entire query.
In pgAdmin, the query is immediate and there is just a pike in the
network traffic when the data is received. That's what I was
expecting to see through psqlODBC also...
Regards
--
Arnaud
