PostGres ODBC too slow

Started by vedant patelabout 2 years ago4 messagesgeneral
Jump to latest
#1vedant patel
vedantpatel297@gmail.com

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,

#2Adrian Klaver
adrian.klaver@aklaver.com
In reply to: vedant patel (#1)
Re: PostGres ODBC too slow

On 3/15/24 3:40 AM, vedant patel wrote:

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.

This will probably get a better answer quicker over at the ODBC list:

https://www.postgresql.org/list/pgsql-odbc/

Let me know in case of any questions or concerns.

Thanks,

--
Adrian Klaver
adrian.klaver@aklaver.com

#3vedant patel
vedantpatel297@gmail.com
In reply to: Adrian Klaver (#2)
Re: PostGres ODBC too slow

Thanks Adrian,

I have been to the articles but it didn't help. Many of them have mentioned
this type of issues but not the solution.

And my main concern is if python library is able to perform fast operation
why ODBC is too much slow. And I have to use ODBC for my application which
is in power builder.

Thanks,

On Fri, 15 Mar, 2024, 11:09 pm Adrian Klaver, <adrian.klaver@aklaver.com>
wrote:

Show quoted text

On 3/15/24 3:40 AM, vedant patel wrote:

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.

This will probably get a better answer quicker over at the ODBC list:

https://www.postgresql.org/list/pgsql-odbc/

Let me know in case of any questions or concerns.

Thanks,

--
Adrian Klaveradrian.klaver@aklaver.com

#4Adrian Klaver
adrian.klaver@aklaver.com
In reply to: vedant patel (#3)
Re: PostGres ODBC too slow

On 3/15/24 10:58 AM, vedant patel wrote:

Thanks Adrian,

I have been to the articles but it didn't help. Many of them have
mentioned this type of issues but not the solution.

That is why you should ask over on the ODBC list, that is where the
folks who develop and use the driver hang out.

When you do you will need to provide more information, at a minimum:

1) Postgres version.

2) ODBC version.

3) Example code.

4) The benchmark results.

And my main concern is if python library is able to perform fast
operation why ODBC is too much slow. And I have to use ODBC for my
application which is in power builder.

Thanks,

On Fri, 15 Mar, 2024, 11:09 pm Adrian Klaver,
<adrian.klaver@aklaver.com> wrote:

On 3/15/24 3:40 AM, vedant patel wrote:

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.

This will probably get a better answer quicker over at the ODBC list:

https://www.postgresql.org/list/pgsql-odbc/

Let me know in case of any questions or concerns.

Thanks,

--
Adrian Klaver
adrian.klaver@aklaver.com

--
Adrian Klaver
adrian.klaver@aklaver.com