| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Markus Wanner <markus(at)bluegap(dot)ch> |
| Cc: | Jens-Wolfhard Schicke <drahflow(at)gmx(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Transaction-controlled robustness for replication |
| Date: | 2008-07-26 09:08:31 |
| Message-ID: | 1217063311.3894.1104.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2008-07-26 at 10:17 +0200, Markus Wanner wrote:
>
> > Expensive as in we need to parse and handle each statement
> separately.
> > If we have a single parameter then much lower overhead.
>
> Is that really much of a concern when otherwise caring about network
> and i/o latency?
I believe so. Jens-Wolfhard has provided the solution it seems.
> And what about sane default settings per session and
> database, so you won't even need to explicitly set them for the
> majority of transactions?
Session pools.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-07-26 09:09:15 | Re: Transaction-controlled robustness for replication |
| Previous Message | Simon Riggs | 2008-07-26 09:05:04 | Re: pg_dump additional options for performance |