pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Pierre C <lists@peufeu.com>
To: Divakar Singh <dpsmails@yahoo.com>
To: Alex Goncharov <alex-goncharov@comcast.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: libpq vs ODBC
Date: Fri, 10 Dec 2010 03:32:24 +0100
Message-ID: <op.vng70ayxeorkce@apollo13> (raw)
In-Reply-To: <E1PQZPa-0000yV-Pd@hanssachs.home>
References: <772237.64789.qm@web65408.mail.ac4.yahoo.com>
<E1PQYd3-0000wW-PB@hanssachs.home>
<254429.23607.qm@web65410.mail.ac4.yahoo.com>
<E1PQZPa-0000yV-Pd@hanssachs.home>
On Thu, 09 Dec 2010 06:51:26 +0100, Alex Goncharov
<alex-goncharov@comcast.net> wrote:
> ,--- You/Divakar (Wed, 8 Dec 2010 21:17:22 -0800 (PST)) ----*
> | 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.
>
> You can't say a "visible impact" unless you can measure it in your
> specific application.
>
> Let's say ODBC takes 10 times of .001 sec for libpq. Is this a
> "visible impact"?
Well you have to consider server and client resources separately. If you
waste a bit of CPU time on the client by using a suboptimal driver, that
may be a problem, or not. It you waste server resources, that is much more
likely to be a problem, because it is multiplied by the number of clients.
I don't know about the specifics of ODBC performance, but for instance
php's PDO driver's handling of prepared statements with postgres comes up
as an example of what not to do.
view thread (7+ messages)
Message-ID: <op.vng70ayxeorkce@apollo13> Permalink: ../op.vng70ayxeorkce@apollo13/ Also on: postgresql.org/message-id/op.vng70ayxeorkce@apollo13 ·
reply
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: lists@peufeu.com, dpsmails@yahoo.com, alex-goncharov@comcast.net Subject: Re: libpq vs ODBC In-Reply-To: <op.vng70ayxeorkce@apollo13> * 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