Re: Standalone synchronous master
От | Joshua D. Drake |
---|---|
Тема | Re: Standalone synchronous master |
Дата | |
Msg-id | 52CDD697.7000800@commandprompt.com обсуждение исходный текст |
Ответ на | Re: Standalone synchronous master (Andres Freund <andres@2ndquadrant.com>) |
Ответы |
Re: Standalone synchronous master
|
Список | pgsql-hackers |
On 01/08/2014 02:46 PM, Andres Freund wrote: >> db0->db1 in synchronous mode >> >> The idea is that we know that data on db0 is not written until we know for a >> fact that db1 also has that data. That is great and a guarantee of data >> integrity between the two nodes. > > That guarantee is never there. The only thing guaranteed is that the > client isn't notified of the commit until db1 has received the data. Well ugh on that.. but that is for another reply. > > That's why you should configure a second standby as another (candidate) > synchronous replica, also listed in synchronous_standby_names. I don't have a response to this that does not involve a great deal of sarcasm. Sincerely, Joshua D. Drake -- Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579 PostgreSQL Support, Training, Professional Services and Development High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc "In a time of universal deceit - telling the truth is a revolutionary act.", George Orwell
В списке pgsql-hackers по дате отправления: