From: | "Benjamin Krajmalnik" <kraj(at)illumen(dot)com> |
---|---|
To: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: psqlodbc-8.2.200 |
Date: | 2006-12-05 16:38:40 |
Message-ID: | F4E6A2751A2823418A21D4A160B68988029D7F@fletch.stackdump.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Running latest release of PostgreSQL ODBC Driver (8.02.0200).
Does the ODBC driver for Windows use connection pooling?
I have a Windows application which is using the driver.
I have connection pooling enabled, and the application notifies the
driver to use connection pooling (per the developer).
I saw a huge disparity when running the queries (a stored procedure
call) via psql locally and via the odbc driver (in this case, I am
referring to the statement duration as logged by postgresql). The call
being made is a "select * from sp_name(parameters)".
I have about an 8:1 performance degradation in the statement duration
when called via ODBC compared to directly in psql (as reported by the
postgres log file).
I have not tried running the query through pgAdmin to see what execution
speed I get.
However, when I turned connection loggin on, I noticed that every single
call to the stored procedure is creating a new connection (so it appears
it is not honoring the connection pooling, which I believe results in
quite a bit of overhead for each statement being called).
TIA,
Benjamin
From | Date | Subject | |
---|---|---|---|
Next Message | noreply | 2006-12-06 16:41:38 | [ psqlodbc-Bugs-1000796 ] client encoding mismatch using ANSI driver with ANSI app |
Previous Message | Patrick Welche | 2006-12-05 11:43:31 | Re: psqlodbc-8.2.200 |