On Fri, Nov 13, 2009 at 3:17 PM, Greg Smith <g...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
