Re: Synchronization levels in SR
От | Robert Haas |
---|---|
Тема | Re: Synchronization levels in SR |
Дата | |
Msg-id | AANLkTilYbYqWnFg_GzfzQrSKcefY1hR8NpfKP3LgWGIj@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Synchronization levels in SR (Fujii Masao <masao.fujii@gmail.com>) |
Ответы |
Re: Synchronization levels in SR
Re: Synchronization levels in SR |
Список | pgsql-hackers |
On Thu, May 27, 2010 at 3:13 AM, Fujii Masao <masao.fujii@gmail.com> wrote: > (1) most standard case: 1 master + 1 "sync" standby (near) > When the master goes down, something like a clusterware detects that > failure, and brings the standby online. Since we can ensure that the > standby has all the committed transactions, failover doesn't cause > any data loss. How do you propose to guarantee that? ISTM that you have to either commit locally first, or send the commit to the remote first. Either way, the two events won't occur exactly simultaneously. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: