Re: replication consistency checking

Поиск
Список
Период
Сортировка
От hydra
Тема Re: replication consistency checking
Дата
Msg-id CAG6MAzTm4FvmENEwDtgSRCyepDNAm3wVq3b-GRG_38UZ0AjNjg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: replication consistency checking  (Jan Lentfer <Jan.Lentfer@web.de>)
Список pgsql-admin


On Tue, Jun 9, 2015 at 10:15 PM, Jan Lentfer <Jan.Lentfer@web.de> wrote:


Am 04.06.2015 um 06:49 schrieb hydra <hydrapolic@gmail.com>:

After setting up streaming replication, is it possible to check whether the slave has the same data as the master?

In the MySQL world there is the percona-toolkit with pt-table-checksum that does this job:
https://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html

Thank you

I have not digged to deep, but as far as I can see from your link:

pt-table-checksum requires statement-based replication, and it sets binlog_format=STATEMENT on the master

And the mysql manual says

If you are using InnoDB tables and the transaction isolation level is READ COMMITTED or READ UNCOMMITTED, only row-based logging can be used. 



So, if I am not misinterpreting, this plays in a different league.
Jan

The recommended binlog format for replication is ROW, so everything except the checks is using ROW and only those checks have STATEMENT set.

В списке pgsql-admin по дате отправления:

Предыдущее
От: hydra
Дата:
Сообщение: Re: replication consistency checking
Следующее
От: hydra
Дата:
Сообщение: Re: replication consistency checking