Robert Haas wrote:
The term of art for making sure that transactions committed on the
primary are visible on the secondary seems to be "one-copy
serializability" (see, for example, a Google Books search on that
term).
Not exactly. 1-copy-serializability which is the standard for
multi-master solutions, guarantees that transactions are executed in the
same serializable order at each replica (which means that transactions
can be executed in different order and committed at different times on
different replica as long as a consistent serializable view is presented
to the client).
There are a number of optimizations in that area but in a multi-master
case, replicas rarely commit at the same time. There are interesting
papers on the subject (like Tashkent & Tashkent+ based on Postgres) for
those who want to understand these problems more thoroughly.
Hope this helps,
manu
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: m...@frogthinker.org
Skype: emmanuel_cecchet
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
