Re: write ahead logging in standby (streaming replication)
От | Fujii Masao |
---|---|
Тема | Re: write ahead logging in standby (streaming replication) |
Дата | |
Msg-id | 3f0b79eb0911130118x230a76cbo301fcfa1c0bd0f0@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: write ahead logging in standby (streaming replication) (Greg Smith <greg@2ndquadrant.com>) |
Список | pgsql-hackers |
On Fri, Nov 13, 2009 at 3:17 PM, Greg Smith <greg@2ndquadrant.com> wrote: > Yeah, that's the "other parts of the industry" I was referring to. MySQL > uses "semi-synchronous" to distinguish between its completely asynchronous > default replication mode and one where it provides a somewhat safer > implementation. The description reads more as "asynchronous with some > synchronous elements", not "one style of synchronous implementation". None > of their documentation wanders into the problem area here by calling it a > true synchronous solution when it's really not--MySQL Cluster is their > synchronous vehicle. > It's fine to adopt the term "semi-synchronous", as it's become quite popular > and people are going to label the PG implementation with it regardless of > what is settled on here. But we should all try to be careful to use it as > correctly as possible. OK. Let's think over what "recv ACK" and "fsync ACK" synchronization modes should be called later. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: