Comments on: Percona Toolkit gripes welcome http://www.xaprb.com/blog/2012/04/17/percona-toolkit-gripes-welcome/ Stay curious! Thu, 02 May 2013 12:36:53 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Justin Rovang http://www.xaprb.com/blog/2012/04/17/percona-toolkit-gripes-welcome/#comment-20023 Justin Rovang Wed, 25 Apr 2012 21:01:03 +0000 http://www.xaprb.com/blog/?p=2722#comment-20023 pt-table-sync –print –ask-pass h=foo.local > diff.sql

Errors and prompts seem to be piped in (e.g.: prompt for password)

]]>
By: Gavin Towey http://www.xaprb.com/blog/2012/04/17/percona-toolkit-gripes-welcome/#comment-20010 Gavin Towey Tue, 24 Apr 2012 20:26:18 +0000 http://www.xaprb.com/blog/?p=2722#comment-20010 Hey Baron,

I’m looking at both 2.0.4 and 2.1.1 and I see the query that uses innodb_locks similar to the one from the manual — That’s good to know. But I don’t see a second query on it.

Thanks for the response! I still like having the full output of the INNODB_LOCKS table =)

]]>
By: Xaprb http://www.xaprb.com/blog/2012/04/17/percona-toolkit-gripes-welcome/#comment-20009 Xaprb Tue, 24 Apr 2012 14:29:57 +0000 http://www.xaprb.com/blog/?p=2722#comment-20009 Ike, yes, thanks — I have those noted now.

]]>
By: Xaprb http://www.xaprb.com/blog/2012/04/17/percona-toolkit-gripes-welcome/#comment-20008 Xaprb Tue, 24 Apr 2012 14:29:33 +0000 http://www.xaprb.com/blog/?p=2722#comment-20008 Gavin, pt-stalk includes a query against those tables and stores the results into the TS-lock-waits file. Can you check that and see if it does what you need? If not, explain more? If you search the source for “INNODB_LOCKS” you will see we execute two queries agains the tables, actually.

I’ve made a note about having arbitrary collectors. Good idea.

]]>
By: Xaprb http://www.xaprb.com/blog/2012/04/17/percona-toolkit-gripes-welcome/#comment-20007 Xaprb Tue, 24 Apr 2012 14:22:14 +0000 http://www.xaprb.com/blog/?p=2722#comment-20007 We get a lot of requests to add features to disable binary logging. Through bitter, bitter, bitter experience we have learned that this is a sure way to completely destroy a percentage of users’ data. Did I mention “bitter” experience? Be careful what you wish for.

]]>