Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rlBWv-000d6z-T3 for pgsql-general@arkaria.postgresql.org; Fri, 15 Mar 2024 17:39:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rlBWu-00AzVT-C0 for pgsql-general@arkaria.postgresql.org; Fri, 15 Mar 2024 17:39:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rlBWs-00AzVG-Jn for pgsql-general@lists.postgresql.org; Fri, 15 Mar 2024 17:39:40 +0000 Received: from fout2-smtp.messagingengine.com ([103.168.172.145]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rlBWf-004gG6-MF for pgsql-general@lists.postgresql.org; Fri, 15 Mar 2024 17:39:37 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.nyi.internal (Postfix) with ESMTP id 5278F1380113; Fri, 15 Mar 2024 13:39:25 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Fri, 15 Mar 2024 13:39:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1710524365; x=1710610765; bh=nuLV/2/yO5 fmy7D+Con6UFt85CTp3lNll5wicuMcbtQ=; b=MZomYMzYmuz82OHQLkpPebj58T sKbcDysqhUk09fOzyaTsiKBmg9hmmbfDTyaUNDtY+zADoFVe76kvG/1VpNFSOREr /Mt6Q2b21eb9MXjxvXwn4sCFvcyRKLyTdIfTag41lEYdorVbRggXIrsLHGycmu87 vDy01mdp+U8D+GjFizThdwRQTvJCtJRewsOPRcAj+9ZIBT2p77P3+LUQgjj5Nw6r erCs4DDPCWiCWDIZWRKM/Ypoxt0TD8djVEc4hpU1WcuuM210g3Sr22XjyKmy4AWG AA9Ke5J9h5Ejc4vYrX5jiTel/Dwx2cQmpBsz99SEexo9W2iwamJQ+mcbvsrg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1710524365; x=1710610765; bh=nuLV/2/yO5fmy7D+Con6UFt85CTp 3lNll5wicuMcbtQ=; b=iQdEAyZBr6+rfn4tjfwNDnbKYI8LwRz5uyL2WwH9iVuI 9XtQFJL+w8kjrQvx+piu0eg3btP0XjioaDMxdvIr/PxuWkoqeZOIXo0Eq7TLTPIa 3x8bX41Kh14MPXE1GniPv9c18a2TszzMyXRg6MfJ0PHkjUbtEip5ym7KBoFzufgW dae7HvpxXcdPK0+aRTO8sldJIQg2kYJrPnSEjWpkZ0LD7XVWKlKDbnjqUBz8qwG5 qTQJ54pQpiaV7fFWpkSNokc1ibmjVPdMlTG7nLqyjRlXQLE3AmplzVIqGM9W4E4n 77Jupdawphyg8wySzEJCWn1W6ODJ1Hswwk/HKchTOg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrjeelgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptgfkffggfgfuvfhfhfgjsegrtderredtvdejnecuhfhrohhmpeetughrihgr nhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh eqnecuggftrfgrthhtvghrnhepleeugfejjeeiffegiefhheevleetkefflefhffeijeff jeejueetiedtieekudegnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgr nhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 15 Mar 2024 13:39:22 -0400 (EDT) Content-Type: multipart/alternative; boundary="------------e2o6irpkpFEvH6trDgFkq0ds" Message-ID: <47c54070-cdc1-461c-9750-e9570a8ba2e4@aklaver.com> Date: Fri, 15 Mar 2024 10:39:20 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: PostGres ODBC too slow To: vedant patel , pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------e2o6irpkpFEvH6trDgFkq0ds Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 --------------e2o6irpkpFEvH6trDgFkq0ds Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit


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
--------------e2o6irpkpFEvH6trDgFkq0ds--