Re: Synchronization levels in SR
| От | Fujii Masao | 
|---|---|
| Тема | Re: Synchronization levels in SR | 
| Дата | |
| Msg-id | AANLkTimPcghz_aDmxxh8mAqwMG2ttb8h+o2qkO8dXMVf@mail.gmail.com обсуждение исходный текст | 
| Ответ на | Re: Synchronization levels in SR (Boszormenyi Zoltan <zb@cybertec.at>) | 
| Ответы | Re: Synchronization levels in SR | 
| Список | pgsql-hackers | 
On Wed, Sep 8, 2010 at 7:04 PM, Boszormenyi Zoltan <zb@cybertec.at> wrote: > Then there is no use to implement individual sync/async > replicated transactions, period. An async replicated transaction > that waits for a sync replicated transaction because of locks > will become implicitely sync. It just waits for another transactions' > sync ack. Hmm.. it's the same with async transaction (i.e., synchronous_commit = false) and sync one (synchronous_commit = true). Async transaction cannot take the lock held by sync one until the sync has flushed the WAL. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: