| From: | Jan Lentfer <Jan(dot)Lentfer(at)web(dot)de> |
|---|---|
| To: | hydra <hydrapolic(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: replication consistency checking |
| Date: | 2015-06-09 20:15:01 |
| Message-ID: | 4623FDBC-612E-46CC-A615-AE1F9CA8C460@web.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> Am 04.06.2015 um 06:49 schrieb hydra <hydrapolic(at)gmail(dot)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.
https://dev.mysql.com/doc/refman/5.6/en/binary-log-setting.html
So, if I am not misinterpreting, this plays in a different league.
Jan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wei Shan | 2015-06-10 06:56:47 | Re: replication consistency checking |
| Previous Message | Jan Lentfer | 2015-06-09 19:47:57 | Re: replication consistency checking |