From: Divakar Singh <dpsmails@yahoo.com>
To: Alex Goncharov <alex-goncharov@comcast.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: libpq vs ODBC
Date: Wed, 8 Dec 2010 21:17:22 -0800 (PST)
Message-ID: <254429.23607.qm@web65410.mail.ac4.yahoo.com> (raw)
In-Reply-To: <E1PQYd3-0000wW-PB@hanssachs.home>
References: <772237.64789.qm@web65408.mail.ac4.yahoo.com>
<E1PQYd3-0000wW-PB@hanssachs.home>
So it means there will be visible impact if the nature of DB interaction is DB
insert/select. We do that mostly in my app.
Performance difference would be negligible if the query is server intensive
where execution time is far more than time taken by e.g. communication interface
or transaction handling.
Am I right?
Best Regards,
Divakar
________________________________
From: Alex Goncharov <alex-goncharov@comcast.net>
To: Divakar Singh <dpsmails@yahoo.com>
Cc: pgsql-performance@postgresql.org
Sent: Thu, December 9, 2010 10:31:17 AM
Subject: Re: [PERFORM] libpq vs ODBC
,--- You/Divakar (Wed, 8 Dec 2010 20:31:30 -0800 (PST)) ----*
| Is there any performance penalty when I use ODBC library vs using libpq?
In general, yes.
In degenerate cases when most of the work happens in the server, no.
You need to measure in the contents of your specific application.
-- Alex -- alex-goncharov@comcast.net --
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dpsmails@yahoo.com, alex-goncharov@comcast.net
Subject: Re: libpq vs ODBC
In-Reply-To: <254429.23607.qm@web65410.mail.ac4.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox