From: Jan Lentfer <Jan.Lentfer@web.de>
To: hydra <hydrapolic@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: replication consistency checking
Date: Tue, 9 Jun 2015 22:15:01 +0200
Message-ID: <4623FDBC-612E-46CC-A615-AE1F9CA8C460@web.de> (raw)
In-Reply-To: <CAG6MAzRaONc703e1PLQZig9PZVuOeLBr=Cc_CsK9ewr-hXbAag@mail.gmail.com>
References: <CAG6MAzRaONc703e1PLQZig9PZVuOeLBr=Cc_CsK9ewr-hXbAag@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
> 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.
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Jan.Lentfer@web.de, hydrapolic@gmail.com
Subject: Re: replication consistency checking
In-Reply-To: <4623FDBC-612E-46CC-A615-AE1F9CA8C460@web.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox