| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Eliot Gable <egable+pgsql-performance(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: C on Client versus C on Server |
| Date: | 2011-04-03 07:01:57 |
| Message-ID: | 4D981B65.8030209@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lars Feistner | 2011-04-04 08:11:41 | Re: very long updates very small tables |
| Previous Message | Eliot Gable | 2011-04-02 18:52:28 | C on Client versus C on Server |