Re: Why PostgreSQL doesn't implement a semi sync replication?
| От | Francisco Olarte |
|---|---|
| Тема | Re: Why PostgreSQL doesn't implement a semi sync replication? |
| Дата | |
| Msg-id | CA+bJJbxDjajKfAinvjB=ujxR0HJKber1nHdPxLCsF=-6oo-SMA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Why PostgreSQL doesn't implement a semi sync replication? (余森彬 <justdoit920823@gmail.com>) |
| Ответы |
Re: Why PostgreSQL doesn't implement a semi sync
replication?
|
| Список | pgsql-hackers |
On Fri, Nov 11, 2016 at 4:40 AM, 余森彬 <justdoit920823@gmail.com> wrote: > As we know, the synchronous commit process is blocked while receives > from acknowledgement from standby in > PostgreSQL.This is good for data consistence in master and standby, and > application can get important data from standby.But > when the standby crash or network goes wrong, the master could be hang.Is > there a feature plan for a semi sync like MySQL > InnoDB(set a timer, and become asynchronous when timeout)? JMO, but it seems this basically means any process should be dessigned to cope with the posibility of not having replicated data after commit, so, why bother with synchronous replication in the first place? Francisco Olarte.
В списке pgsql-hackers по дате отправления: