| From: | Markus Wanner <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Boszormenyi Zoltan <zb(at)cybertec(dot)at> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Synchronization levels in SR |
| Date: | 2010-09-08 12:47:35 |
| Message-ID: | 4C8785E7.8070803@bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/08/2010 12:04 PM, Boszormenyi Zoltan wrote:
> Then there is no use to implement individual sync/async
> replicated transactions, period.
I disagree. Different transactions have different priorities for latency
vs. failure-resistance.
> An async replicated transaction
> that waits for a sync replicated transaction because of locks
> will become implicitely sync.
Sure. But how often do your transactions wait for another one because of
locks? What do we have MVCC for?
Regards
Markus Wanner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-09-08 12:56:23 | Re: Synchronization levels in SR |
| Previous Message | Fujii Masao | 2010-09-08 12:30:34 | Re: Synchronization levels in SR |