Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z2PvX-0000eo-08 for pgsql-admin@arkaria.postgresql.org; Tue, 09 Jun 2015 20:15:15 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Z2PvW-0001dM-An for pgsql-admin@arkaria.postgresql.org; Tue, 09 Jun 2015 20:15:14 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Z2PvV-0001cL-E4 for pgsql-admin@postgresql.org; Tue, 09 Jun 2015 20:15:13 +0000 Received: from mout.web.de ([212.227.15.14]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.84) (envelope-from ) id 1Z2PvR-0002r3-Sx for pgsql-admin@postgresql.org; Tue, 09 Jun 2015 20:15:12 +0000 Received: from vm-mailsrv.lan.net ([87.155.107.154]) by smtp.web.de (mrweb004) with ESMTPSA (Nemesis) id 0MRA59-1YcFwC0aWV-00Ue3Y; Tue, 09 Jun 2015 22:15:07 +0200 Received: from localhost (localhost [127.0.0.1]) by vm-mailsrv.lan.net (Postfix) with ESMTP id 855F3359E2; Tue, 9 Jun 2015 22:15:06 +0200 (CEST) X-Spam-Flag: NO X-Spam-Score: -2.896 X-Spam-Level: X-Spam-Status: No, score=-2.896 tagged_above=-99.9 required=6.31 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from vm-mailsrv.lan.net ([127.0.0.1]) by localhost (vm-mailsrv.lan.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zeyX8xHYMsom; Tue, 9 Jun 2015 22:15:02 +0200 (CEST) Received: from [10.94.76.50] (ipad.lan.net [10.94.76.50]) by vm-mailsrv.lan.net (Postfix) with ESMTP id 22E2D288A9; Tue, 9 Jun 2015 22:15:02 +0200 (CEST) Content-Type: multipart/alternative; boundary=Apple-Mail-B5E48C3E-568C-494B-A7C7-D4DEF464B7CD Mime-Version: 1.0 (1.0) Subject: Re: replication consistency checking From: Jan Lentfer X-Mailer: iPad Mail (12D508) In-Reply-To: Date: Tue, 9 Jun 2015 22:15:01 +0200 Cc: "pgsql-admin@postgresql.org" Content-Transfer-Encoding: 7bit Message-Id: <4623FDBC-612E-46CC-A615-AE1F9CA8C460@web.de> References: To: hydra X-Provags-ID: V03:K0:mNPp/IKpe11LmJnHDcV343MR2YVfmDewHDPVbwjGWk//YLX4YDu mM9SnojbYY41nwOoO8iuMMEI3Iple2SM56Foi8j8zxM+hqDNbW/5Q1cfwo434LdaFz122z8 696+oIyJfi565thX8IvMJELPsBVMLBOwJRYo6U2X20505k243I1lH7t8Tp7GDqAJ0kjFumR 4RMdhFLf7U76c7wHobJBg== X-UI-Out-Filterresults: notjunk:1;V01:K0:WbobMBnqnIU=:FGoWvnjxvvWtsXXagGSbbV AbClLM55YGLeVWy/QL3bkGzG45pv24FXitckyLBG5k07ynbABFVl31k0hsn9IqRb9SeaSGzwg wfK1kUYe51NT98iC2GmDcNhhf/jJ9L8PL1vH4duHcqtkV9TvrKl4o/ILJ2tgPRdtBn+atdjJt DZqSdzntgmh2IG7lYuxTQOXf3trT817swMJnY6Ea2NSBFByzsJ7YN6JxSYerdeqWdbx+n/xcb 5nr+nCYyoAbbGc7WiBJM5cUmk6xNtByQNqRXAaSyewhE1YXIeRrMAHMAdZ6mha2zH+pi0roHX OY6aKxU38sCZw5YoxejiDJWn9F//OWGI3YpvbGT86OZA2HcDJzRfM4/yxKALveLwMow4V3Lmu 2qWncCnMujbtkqlMbOP/MaoBV0oHi8jrCN56v7egbd8iPWoffkwz9YeAAHPox91es6K4Rlxi5 RUoMZO3PMs6newEYCz4Jc33u7QuTF9v7diAr4hwGdXYERdhY+UQy1BrIAREqfLTNLX0T22wx3 N7R7l71uM+3/HJeECBJhFcJ0AwGB53TKUngxsCasQdRtXtVE5Wx2d82TSyuH9valNnbVNTZj1 g5aNps0875GjcRbKLg9WOGVikcSL1UevsklVZ9Kw/ZDoQ8Iey6e1xDbZArpU1ttxjPqvgafxj 8YaDxd5Cf3psI8NZUGhcscTVzVLZzDZh6tg1vSidNTQLgAyOhevk48exxrZacsGNkcaY= X-Pg-Spam-Score: -3.0 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --Apple-Mail-B5E48C3E-568C-494B-A7C7-D4DEF464B7CD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable > Am 04.06.2015 um 06:49 schrieb hydra : >=20 > After setting up streaming replication, is it possible to check whether th= e slave has the same data as the master? >=20 > In the MySQL world there is the percona-toolkit with pt-table-checksum tha= t does this job: > https://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html >=20 > 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_f= ormat=3DSTATEMENT on the master And the mysql manual says If you are using InnoDB tables and the transaction isolation level is READ C= OMMITTED or READ UNCOMMITTED, only row-based logging can be used.=20 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 --Apple-Mail-B5E48C3E-568C-494B-A7C7-D4DEF464B7CD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable


Am 04.06.2015 um 06= :49 schrieb hydra <hydrapolic@gma= il.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 t= he percona-toolkit with pt-table-checksum that does this job:
http= s://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 s= ee from your link:

pt-table-checksum require= s statement-based replication, and it sets binlog_format=3D= STATEMENT = ;on the master

And the mysql manual say= s

= If you are using&n= bsp;In= noDB tables and the transaction isolation level is READ COMMITTED or READ UNCOMMITTED, only row-based logging can= be used. 



So, if I am no= t misinterpreting, this plays in a different league.
Jan



= --Apple-Mail-B5E48C3E-568C-494B-A7C7-D4DEF464B7CD--