Re: C on Client versus C on Server - Mailing list pgsql-performance

From Heikki Linnakangas
Subject Re: C on Client versus C on Server
Date
Msg-id 4D981B65.8030209@enterprisedb.com
Whole thread Raw
In response to C on Client versus C on Server  (Eliot Gable <egable+pgsql-performance@gmail.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Eliot Gable
Date:
Subject: C on Client versus C on Server
Next
From: Lars Feistner
Date:
Subject: Re: very long updates very small tables