From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Eliot Gable <egable+pgsql-performance@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: C on Client versus C on Server
Date: Sun, 03 Apr 2011 10:01:57 +0300
Message-ID: <4D981B65.8030209@enterprisedb.com> (raw)
In-Reply-To: <BANLkTi=2EpfSK94LK=2hWSVxBCjV3hfacQ@mail.gmail.com>
References: <BANLkTi=2EpfSK94LK=2hWSVxBCjV3hfacQ@mail.gmail.com>
On 02.04.2011 21:52, Eliot Gable wrote:
> 1) Each select statement from the User Client C Module would be a separate
> transaction which would drastically increase transaction overhead for the
> whole set of requests.
You could wrap the statements in BEGIN-COMMIT in the client code.
> 2) Writing the billing data at the end would mean that I not only have to
> pull all the data down to the User Client, I must also push the data back up
> to the server for writing the billing records.
Yeah, that sounds right.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
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: heikki.linnakangas@enterprisedb.com, egable+pgsql-performance@gmail.com
Subject: Re: C on Client versus C on Server
In-Reply-To: <4D981B65.8030209@enterprisedb.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