MIME-Version: 1.0
From: vedant patel <vedantpatel297@gmail.com>
Date: Mon, 18 Mar 2024 11:47:03 +0530
Message-ID: 
 <CAL4ovZoYjU0NiHg+aYYvzzPChjyYpFGyWt8QwDvkvt91UessZA@mail.gmail.com>
Subject: PostGres ODBC too slow
To: pgsql-odbc@postgresql.org
Content-Type: multipart/alternative; boundary="00000000000002aa530613e94f15"
Archived-At: 
 <https://www.postgresql.org/message-id/CAL4ovZoYjU0NiHg%2BaYYvzzPChjyYpFGyWt8QwDvkvt91UessZA%40mail.gmail.com>
Precedence: bulk

--00000000000002aa530613e94f15
Content-Type: text/plain; charset="UTF-8"

Hello There,

Recently, we've encountered some performance issues with the ODBC driver
provided by Postgres. Upon investigation, we noticed that switching from
the UNICODE to ANSI driver resulted in performance improvements for some
queries, albeit at the expense of others.

To delve deeper into this matter, I conducted tests using a Python script
with the psycopg2 library, and the results were significantly better.
However, to address this issue comprehensively, I've explored alternative
ODBC drivers available in the market. While some minor improvements were
observed in a few queries with a different driver, the overall performance
remains a concern.

Given your extensive experience in this area, I would greatly appreciate
your insights and recommendations on which ODBC driver would be most
suitable for our use case. Any advice or suggestions you could offer would
be immensely helpful in resolving this performance issue.

Let me know in case of any questions or concerns.

Thanks,

--00000000000002aa530613e94f15
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"auto" style=3D"color:rgb(11,83,148);font-famil=
y:verdana,sans-serif;font-size:12.8px">Hello=C2=A0There,</div><div dir=3D"a=
uto" style=3D"color:rgb(11,83,148);font-family:verdana,sans-serif;font-size=
:12.8px"><br></div><div dir=3D"auto" style=3D"color:rgb(11,83,148);font-fam=
ily:verdana,sans-serif;font-size:12.8px">Recently, we&#39;ve encountered so=
me performance issues with the ODBC driver provided by Postgres. Upon inves=
tigation, we noticed that switching from the UNICODE to ANSI driver resulte=
d in performance improvements for some queries, albeit at the expense of ot=
hers.<br><br>To delve deeper into this matter, I conducted tests using a Py=
thon script with the psycopg2 library, and the results were significantly b=
etter. However, to address this issue comprehensively, I&#39;ve explored al=
ternative ODBC drivers available in the market. While some minor improvemen=
ts were observed in a few queries with a different driver, the overall perf=
ormance remains a concern.<br><br>Given your extensive experience in this a=
rea, I would greatly appreciate your insights and recommendations on which =
ODBC driver would be most suitable for our use case. Any advice or suggesti=
ons you could offer would be immensely helpful in resolving this performanc=
e issue.<br><br></div><span style=3D"font-size:12.8px;color:rgb(80,0,80);fo=
nt-family:arial,helvetica,sans-serif"><div style=3D"font-family:verdana,san=
s-serif;color:rgb(11,83,148)">Let me know in case of any questions or conce=
rns.=C2=A0</div><div style=3D"font-family:verdana,sans-serif;color:rgb(11,8=
3,148)"><br></div></span><div dir=3D"auto" style=3D"color:rgb(11,83,148);fo=
nt-family:verdana,sans-serif;font-size:12.8px">Thanks,</div></div>

--00000000000002aa530613e94f15--